Skip to content
StackBlazeDocs

Observability

Built-in metrics and logs, plus how to forward telemetry to your existing stack.

Coroot

Section titled “Coroot”

Observability is Coroot (eBPF metrics, logs, and traces). Open it from an app in the dashboard — StackBlaze mints a one-time handoff and opens Coroot in a new tab. Billing and in-dashboard charts query PromQL query_range with an API key; there is no instant /query endpoint.

Coroot handoff Open observability from a service · one-time token Service dashboard tile One-time handoff minted, then opens a tab Coroot eBPF metrics, logs, and traces Metrics Logs Traces Map Billing charts in the dashboard PromQL query_range X-API-Key · no instant /query your own OpenTelemetry exporters stay independent of Coroot
Signal Use it for
CPU and RSS memory Right-sizing pod sizes and catching OOMs
TCP egress (eBPF) Unexpected outbound traffic
Golden signals / incidents Error rate and latency regressions after a deploy
Service map Who talks to whom inside the phase

Logs

Section titled “Logs”

Runtime stdout/stderr is in the app Logs tab and via GET /api/logs/{pipeline}/{phase}/{app}/. Search uses the durable log index (search_logs in MCP / chat). An empty live tail is not the same as “no logs” — search history when the pod has rotated.

Notifications

Section titled “Notifications”

Configure Slack, Discord, or generic webhooks under Settings → Notifications. Pick pipelines and event names (deploys, failures). This is not a full PagerDuty product — use Coroot incidents for SLO-style alerts.

Your own exporters

Section titled “Your own exporters”

You can still emit OpenTelemetry from the app to Datadog, Honeycomb, or Grafana Cloud. That is in-process and independent of Coroot.

After a bad deploy

Section titled “After a bad deploy”

Open Coroot from the app, then roll back from Rollbacks or POST /api/deployments/rollback/{pipeline}/{phase}/{app}/{revisionId}.

Deep dive: Observability beyond metrics