Observability — pointer¶
The canonical operator-facing wiring lives at ../observability.md. The OTel pipeline diagram lives at ../architecture/tracing-flow.md. Day-to-day operator how-to (Grafana panels, Loki queries, trace correlation) lives at observability-runbook.md.
This page exists only so the engineering track has a discoverable starting point.
Quick lookup¶
| I want to… | Go to |
|---|---|
Understand the OTel SDK bootstrap (where @opentelemetry/sdk-node initialises, why pre-otel.main.ts is first) |
../observability.md §"How traces are produced" |
| Read the Mermaid pipeline diagram | ../architecture/tracing-flow.md |
| Know which Grafana dashboards exist + what each shows | ../observability.md §Dashboards |
| Validate trace ↔ log correlation locally | ../observability.md §"Validating correlation" |
| Operator day-to-day (perf run, dashboards, Loki queries) | observability-runbook.md |
Browser RUM via @vercel/otel (ebit-fe) |
../observability.md §"The wiring (Next.js)" |
Decide between pino and EvoLogger (winston) |
ADR-0001 |
| Understand why we use spanmetrics vs Prisma metrics | ADR-0002 |
| Storage budget for Jaeger v2 / Badger | ADR-0009 |
| Tail-sampling policy | ADR-0012 |
Configuration files (in repo root)¶
observability/otel-collector.yml— OTel Collector pipeline (receivers, processors, exporters, spanmetrics connector, filelog/docker for EvoLogger).observability/loki.yml,observability/prometheus.yml— backend configs.observability/grafana/provisioning/— datasources + dashboards as code.
Related¶
- Performance methodology:
../performance-testing.md. - Perf-test report:
../performance-test-report.md. - Engineering index:
README.md.