slug: opentelemetry
provider: OpenTelemetry
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: Logs
  spec_file: opentelemetry-logs-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.88
  evidence: POST /v1/logs exportLogs 'OpenTelemetry Export log data'; schemas LogRecord, ResourceLogs
  reason: OTLP log export is telemetry ingestion for running services, which is precisely Observability
    Management (logs, metrics, traces) under SaaS Platform Operations.
- tag: Metrics
  spec_file: opentelemetry-metrics-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.88
  evidence: POST /v1/metrics exportMetrics 'OpenTelemetry Export metric data'; schemas Gauge, Histogram,
    ResourceMetrics
  reason: Metric export for cloud-native services is observability instrumentation/collection, not business
    KPI reporting.
- tag: Traces
  spec_file: opentelemetry-traces-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.88
  evidence: POST /v1/traces exportTraces 'OpenTelemetry Export trace data'; schemas Span, SpanLink, ResourceSpans
  reason: Distributed trace export is core observability tooling for production services.