slug: datadog-apm
provider: Datadog APM
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: 6
edges:
- tag: Service Level Objectives
  spec_file: datadog-apm-service-level-objectives-api-openapi.yml
  capability_id: BC-4220.10
  capability_id_l1: BC-4220
  capability_name: Service Reliability Engineering
  confidence: 0.92
  evidence: POST /api/v1/slo CreateSLO 'Create an SLO object'; GET /api/v1/slo/{slo_id}/history 'Get an
    SLO's history'; schema 'ServiceLevelObjectiveRequest'
  reason: The surface is the full lifecycle of service level objectives and their attainment history,
    which is exactly definition and stewardship of service-level indicators and objectives for a running
    service.
- tag: Service Level Objective Corrections
  spec_file: datadog-apm-service-level-objective-corrections-api-openapi.yml
  capability_id: BC-4220.10
  capability_id_l1: BC-4220
  capability_name: Service Reliability Engineering
  confidence: 0.85
  evidence: POST /api/v1/slo/correction CreateSLOCorrection 'Create an SLO correction'; schema 'SLOCorrectionCategory'
  reason: SLO corrections adjust service-level objective calculations (e.g. excluding maintenance windows),
    which is stewardship of SLIs/SLOs and error budgets — Service Reliability Engineering.
- tag: Spans
  spec_file: datadog-apm-spans-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.85
  evidence: POST /api/v2/spans/analytics/aggregate AggregateSpans 'Aggregate spans'; POST /api/v2/spans/events/search
    ListSpans 'Search spans'
  reason: Searching and aggregating distributed-trace spans is core trace-based observability of the running
    service, matching Observability Management (logs, metrics, traces).
- tag: Spans Metrics
  spec_file: datadog-apm-spans-metrics-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.78
  evidence: POST /api/v2/apm/config/metrics CreateSpansMetric 'Create a span-based metric'; schema 'SpansMetricComputeAggregationType'
  reason: Defining metrics derived from trace spans produces operational metrics for monitoring production
    services — observability instrumentation and tooling rather than product usage analytics.
- tag: APM
  spec_file: datadog-apm-apm-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.75
  evidence: GET /api/v2/apm/services GetServiceList 'Get service list'; 'The APM, retention filter, span,
    span-metric and service-definition surface'
  reason: Datadog APM is distributed tracing and production performance monitoring; listing APM-instrumented
    services is part of making the running service understandable in production (Observability Management).
    Only one operation, so some ambiguity about the narrower sub-capability.
- tag: APM Retention Filters
  spec_file: datadog-apm-apm-retention-filters-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.72
  evidence: GET /api/v2/apm/config/retention-filters ListApmRetentionFilters 'List all APM retention filters';
    schema 'SpansFilter'
  reason: These operations govern which APM trace spans are retained for analysis — configuration of the
    tracing/telemetry pipeline, i.e. observability tooling management. Not product usage telemetry (BC-4280)
    because the data are operational traces, not product analytics events.