observability

Debug missing periodic jobs and silent triggers by running navigator doctor, then correlating logs, traces, and Restate invocations to trace the failure from telemetry signals to the underlying service or scheduling issue.

Safe telemetry instrumentation requires recording only identifiers and counts instead of sensitive content when adding spans, metrics, or log fields to service binaries.

Set up unified telemetry initialization through one shared telemetry entry point to standardize how binaries initialize logs, traces, and metrics before exporting.

Yes, telemetry export works with BigQuery and the OTel Collector when OTLP export is configured, allowing you to deliver logs, traces, and metrics to either destination for operational debugging.

Workflow handler instrumentation may not show up in traces if it lacks identifier-only spans, uses sensitive content instead of identifiers, or lacks shared telemetry initialization with OTLP export configured.

Diagnose unready workloads and workflow failures by correlating telemetry signals across logs, BigQuery, and the Restate console, using navigator doctor investigations to pinpoint the root cause.