CuraDevOps

tag: Distributed-Tracing · 2 items

Plan archived Tempo 3.1 adds Kafka TLS/SASL, trace redaction, and TraceQL metrics updates
2026-10-01 · Grafana Blog · source ↗ #observability#distributed-tracing#kafka
  • Platform/SRE — Plan: Platform teams running Tempo 3.0 in microservices mode with Kafka-based ingestion shipped without TLS support — a real security gap. Upgrading to 3.1 closes it with TLS and additional SASL mechanisms (SCRAM-SHA-256/512, OAUTHBEARER, AWS_MSK_IAM); schedule the upgrade this quarter if Kafka ingestion is in use.
  • CI/CD — Skip
  • Leader — Skip
Plan archived Tempo 3.0: Kafka-native architecture, RF3 removed, TraceQL metrics GA
2026-07-12 · Grafana Blog · source ↗ #distributed-tracing#observability#grafana
  • 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)