slug: tempo
provider: Tempo
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Software & Technology
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 3
edges:
- tag: Traces
  spec_file: tempo-traces-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.85
  evidence: 'GET /api/traces/{traceID}  getTrace  Get Trace By ID; schemas: Trace, Span'
  reason: Retrieval of distributed traces and spans is squarely observability management (logs, metrics,
    traces) for a running service.
- tag: Metrics
  spec_file: tempo-metrics-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.75
  evidence: 'GET /api/metrics/query_range  queryMetricsRange  Query Metrics Range; schemas: MetricsResult
    — ''generating metrics from trace data'''
  reason: Tempo is a distributed tracing backend; this endpoint serves metrics derived from traces, which
    is production observability (logs, metrics, traces) rather than any financial or business metric.
- tag: Search
  spec_file: tempo-search-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.75
  evidence: GET /api/search  searchTraces  Search Traces; 'searching spans with TraceQL'
  reason: Generic 'Search' tag, but the operation searches distributed trace spans — part of making the
    running service understandable in production (observability), not a general search utility over business
    records.