Open Code Review (OCR) — Telemetry
Opt-in observability — review duration, per-tool-call timing, token usage — layered on top of the functional code paths, never load-bearing for a review's result. Package: internal/telemetry/.
What flows through it
Technical details
Package: internal/telemetry/
Depends on: llm
Depended on by: (nothing in this package set imports it directly — used only by the CLI entry point or externally)
What actually happens here
config.go/provider.go set up the OTLP exporter from environment configuration (no telemetry runs unless configured); span.go/events.go/metrics.go are thin wrappers called from every other package's hot paths (StartSpan, Event, RecordToolCall, RecordLLMRequest) so instrumentation reads as ordinary function calls rather than a cross-cutting framework.
How the LLM / model version is chosen
No model calls — and telemetry data itself must never include secrets: API keys and auth headers are explicitly excluded from every event/span per ASSURANCE_CASE.md.
Deterministic (non-LLM) work in this module
All of it — span/event emission is deterministic instrumentation code with no influence on review outcomes.
Part of the module docs index. Full interactive version, with every module
side by side: architecture.html §7. Cross-cutting mechanisms
this module participates in (retry, compression, manifest, resume, hashing): LLD.