Docs PR check: merged Tempo PRs for 2026-06-01 to 2026-06-08

Evaluated merged PRs in grafana/tempo for the previous 7 days from the automation trigger:

• Window start: 2026-06-01T13:00:19Z
• Window end: 2026-06-08T13:00:19Z
• Skill: .claude/skills/docs-pr-check/SKILL.md
• Source query: merged:>=2026-06-01T13:00:19Z merged:<2026-06-08T13:00:19Z
• Total PRs evaluated: 53

Table

Gap summary

Prioritized documentation work:

1. PR grafana/tempo#7199: update TraceQL metrics math docs for scalar operands.

   • This is the highest-priority gap because current docs explicitly say scalar operands are unsupported, which is now incorrect.
   • Update docs/sources/tempo/metrics-from-traces/metrics-queries/functions.md.
   • Suggested changes:
     • Remove or rewrite the limitation that says scalar operands are unsupported.
     • Add examples such as ({} | rate()) * 100, 100 * (({status=error} | rate()) / ({} | rate())), and ({} | count_over_time() by(.service.name)) * 100.
     • Document parser constraints from the PR tests: metrics pipelines must be parenthesized for scalar math (({} | rate()) * 5 is valid; {} | rate() + 5 is not), bare constant expressions are not TraceQL metrics queries, and duration operands are rejected.

2. PR grafana/tempo#7362: document Prometheus-based KEDA autoscaling for metrics-generator Jsonnet.

   • Adds the user-facing _config.metrics_generator.keda.query option.
   • Existing Tanka docs only describe CPU-based metrics-generator KEDA and state that metrics-generator uses a CPU trigger.
   • Update docs/sources/tempo/set-up-for-tracing/setup-tempo/deploy/kubernetes/tanka.md.
   • Suggested changes:
     • Explain that an empty metrics_generator.keda.query keeps the existing CPU trigger using target_cpu.
     • Explain that a non-empty metrics_generator.keda.query creates a Prometheus trigger using metricType: Value and threshold: 1, so the PromQL result must be the desired replica count.
     • Document that autoscaling_prometheus_url is required for this mode and include or adapt the example query from operations/jsonnet/microservices/autoscaling.libsonnet.

3. PR grafana/tempo#7207: add the Service Topology dashboard to mixin dashboard docs.

   • Adds operations/tempo-mixin-compiled/dashboards/tempo-service-graph.json and example dashboard content.
   • docs/sources/tempo/operations/monitor/_index.md still says the mixin has eight dashboards and does not include this new dashboard.
   • Suggested changes:
     • Update the dashboard count and add a ### Tempo Service Topology dashboard section with the file name tempo-service-graph.json.
     • Explain that the dashboard visualizes service topology using traces_service_graph_connection_info.
     • Cross-link to docs/sources/tempo/metrics-from-traces/service_graphs/_index.md, especially the service-graphs-connection-info subprocessor setup.
     • Consider updating docs/sources/tempo/shared/metamonitoring.md, which also says to install all eight dashboards.

No PRs were classified as "Docs needed" with entirely missing new documentation. The actionable gaps above are "Docs update needed" items where existing docs are incomplete or stale.