Plan
active
Tempo 3.0: Kafka-native architecture, RF3 removed, TraceQL metrics GA
- Platform/SRE — Plan: This GA major release changes how Tempo is deployed at scale — removing the RF3 requirement reduces storage overhead and the new Kafka-compatible architecture decouples read/write paths. Teams running Tempo should schedule an upgrade evaluation this quarter to assess the operational and cost impact.
- CI/CD — Skip
- Leader — Learn: The RF3 removal and new architecture lower the infrastructure cost of running distributed tracing at scale, which is a useful data point if Tempo is part of the observability standard — but no strategic decision is forced by this release.
- Signals: GA announcement · major release (3.0)
This entry was curated and judged by AI (Claude) with automated enrichment
(CISA KEV / EPSS / public PoC). Verify against the original source before
acting. Found a bad verdict?
Report it —
confirmed errors go to the corrections log.