o2r packaging: tempo_grafana layer - tooling container + Tempo/Grafana chart #49
Labels
No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set.
Reference
coilyco-flight-deck/otel-a2a-relay#49
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of #45 (per-layer isolated-unit packaging).
Layer:
tempo_grafana(otel-a2a-relay-tempo-grafanav0.3.0) - Tempo + Grafana backend extension. Shipso2r-tempo-harness+ abootstrapwrapper, plus the dockerized Tempo + Prometheus + Grafana stack with provisioned datasource and two auto-loaded dashboards (o2r-overview, LUCA-flow).Today the stack is a
docker/docker-compose.ymlof upstream images with provisioning files (tempo.yaml,prometheus.yaml,grafana/). This issue ports that into an isolated tooling image + a chart.Docker
o2r-tempo-harness) for harness/probe runs. Image ref192.168.0.194:30500/otel-a2a-relay-tempo-grafana:<git-sha>.Helm
tempo_grafana/chart/: Tempo + Prometheus + Grafana Deployments/Services, carrying the existing provisioning as ConfigMaps - Tempometrics_generator-> Prometheus remote_write, Grafana datasource + both dashboards.Acceptance
helm installbrings up Tempo+Prometheus+Grafana with the o2r-overview and LUCA-flow dashboards present and the datasource wired - traces from a LUCA run land and render.Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag:
burndown-2026-06.