-
Notifications
You must be signed in to change notification settings - Fork 208
Phase 3: per-engine OTLP tracing integrations #3766
Copy link
Copy link
Open
Labels
area/monitoringIssues or PRs related to the monitoring stack (vlogs, vmstack, grafana, workloadmonitor)Issues or PRs related to the monitoring stack (vlogs, vmstack, grafana, workloadmonitor)kind/featureCategorizes issue or PR as related to a new featureCategorizes issue or PR as related to a new featurepriority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to completeImportant over the long term, but may not be staffed and/or may need multiple releases to completetriage/acceptedIndicates an issue is ready to be actively worked onIndicates an issue is ready to be actively worked on
Description
Activity
Metadata
Metadata
Assignees
Labels
area/monitoringIssues or PRs related to the monitoring stack (vlogs, vmstack, grafana, workloadmonitor)Issues or PRs related to the monitoring stack (vlogs, vmstack, grafana, workloadmonitor)kind/featureCategorizes issue or PR as related to a new featureCategorizes issue or PR as related to a new featurepriority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to completeImportant over the long term, but may not be staffed and/or may need multiple releases to completetriage/acceptedIndicates an issue is ready to be actively worked onIndicates an issue is ready to be actively worked on
Summary
Phase 3 of distributed tracing (epic #3761, design cozystack/community#38): wire each supported managed engine to emit OTLP spans to the per-tenant collector (
otel-traces.<tenant-ns>.svc:4317, from phase 2 #3763). One PR per engine, all linked here.Per the design's §4 per-engine breakdown, depth and mechanism differ per engine:
opentelemetry_span_logsystem table (currently disabled viaremove="1"); re-enable + add an OTLP export path.pg_tracingextension (or client-side); a sidecar cannot produce statement-level spans.Cross-cutting decision (from the design's open question)
Enablement follows the metrics model (platform-configured), not a per-app
tracing.enabledtoggle; the OTLP endpoint is platform-decided (the in-namespace collector Service), never carried in app values. The concrete Application→HelmRelease wiring is established by the first engine PR (ClickHouse) and reused by the rest.Tracked under epic #3761.