What problem does it solve?
It helps you verify that Navigator is emitting traces, logs, and metrics correctly by showing them in a local Grafana LGTM stack instead of guessing from stdout or waiting for production.
Core Features & Use Cases
- Automatic local observability stack: Starts Grafana, Loki, Tempo, Prometheus, and the bundled OTel Collector as part of the KIND development flow.
- Cross-service trace inspection: Confirms trace propagation from web into workflows-service across the Restate boundary.
- Safe telemetry validation: Verifies identifiers, counts, statuses, and durations without logging client content or legal text.
- Use case: Check that a new span, counter, or log field appears in Grafana before shipping a change to production.
Quick Start
Run navigator start-dev-server, generate a request or workflow, and open Grafana at http://localhost:3000 to inspect the resulting traces, logs, and metrics.