slug: dash0 provider: Dash0 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: 10 edges: - tag: Manage SLOs (Private BETA) spec_file: dash0-manage-slos-private-beta-api-openapi.yml capability_id: BC-4220.10 capability_id_l1: BC-4220 capability_name: Service Reliability Engineering confidence: 0.92 evidence: POST /api/slos 'Create an SLO'; schemas SloObjective, SloIndicatorSpec, SloAlertCondition reason: Service-level objectives and indicators with alert policies are exactly service reliability engineering (SLI/SLO/error-budget stewardship). - tag: Query Telemetry spec_file: dash0-query-telemetry-api-openapi.yml capability_id: BC-4220.20 capability_id_l1: BC-4220 capability_name: Observability Management confidence: 0.88 evidence: POST /api/logs 'Returns OTLP logs records'; POST /api/trace/details 'Returns the OTLP spans and log records (if any) associated with the trace ID' reason: Operations query logs, spans and traces from an OpenTelemetry-native observability platform — this is exactly logs/metrics/traces observability of a running service (BC-4220.20), not business monitoring of any other domain. - tag: Manage Synthetic Checks spec_file: dash0-manage-synthetic-checks-api-openapi.yml capability_id: BC-4220.20 capability_id_l1: BC-4220 capability_name: Observability Management confidence: 0.85 evidence: POST /api/synthetic-checks 'Create a synthetic check'; GET /api/synthetic-checks/locations; schemas SyntheticHttpCheckAssertions reason: Synthetic monitoring of endpoints from check locations is explicitly part of observability management (synthetic monitoring). - tag: Prometheus API spec_file: dash0-prometheus-api-api-openapi.yml capability_id: BC-4220.20 capability_id_l1: BC-4220 capability_name: Observability Management confidence: 0.8 evidence: GET /api/prometheus/api/v1/query 'Evaluates an instant query at a single point in time'; 'Returns metadata about metrics currently scraped from targets' reason: PromQL query surface over ingested metrics — reading production metrics, i.e. observability management of the running service. - tag: Manage Recording Rules spec_file: dash0-manage-recording-rules-api-openapi.yml capability_id: BC-4220.20 capability_id_l1: BC-4220 capability_name: Observability Management confidence: 0.78 evidence: POST /api/recording-rules — 'Create a recording rule'; schemas PrometheusRule, PrometheusRuleGroup, PrometheusRuleSpec reason: Prometheus recording rules pre-compute metric series for an observability platform; this is metrics/observability configuration of the running service, not a business rules engine. - tag: Manage Alerting spec_file: dash0-manage-alerting-api-openapi.yml capability_id: BC-4220.20 capability_id_l1: BC-4220 capability_name: Observability Management confidence: 0.72 evidence: '"Create a new check rule"; "Retrieve a specific check rule (Prometheus alert rule) by its origin or id"; schemas PrometheusAlertRule, CheckThresholds' reason: Managing Prometheus alert rules and check thresholds is monitoring configuration on an observability platform — not financial-crime or any other domain alerting. Sub-capability choice between Observability Management and Incident Response detection is genuinely arguable, hence 0.72. - tag: Manage Dashboards spec_file: dash0-manage-dashboards-api-openapi.yml capability_id: BC-4220.20 capability_id_l1: BC-4220 capability_name: Observability Management confidence: 0.72 evidence: '"Create a dashboard"; "Import a dashboard"; schemas DashboardDefinition, DashboardMetadata, Dataset' reason: Dashboards here visualise logs, metrics and traces of the running service, which is observability tooling rather than management reporting (BC-230.30) of business KPIs. Moderate confidence because the dashboard schema itself is domain-neutral. - tag: Manage Sampling Rules spec_file: dash0-manage-sampling-rules-api-openapi.yml capability_id: BC-4220.20 capability_id_l1: BC-4220 capability_name: Observability Management confidence: 0.72 evidence: POST /api/sampling-rules 'Create a new sampling rule'; schemas SamplingConditionProbabilistic, SamplingRateLimit reason: Probabilistic/error-based sampling rules govern how telemetry (traces/logs) is retained in the observability pipeline — observability management, not product usage telemetry governance. - tag: Manage Signal To Metrics (BETA) spec_file: dash0-manage-signal-to-metrics-beta-api-openapi.yml capability_id: BC-4220.20 capability_id_l1: BC-4220 capability_name: Observability Management confidence: 0.72 evidence: POST /api/signal-to-metrics 'Create a new signal-to-metrics config'; schemas SignalToMetricsSpec, SignalToMetricsOutput reason: Deriving metrics from ingested telemetry signals is configuration of logs/metrics/traces processing for production observability. - tag: Manage Notification Channels spec_file: dash0-manage-notification-channels-api-openapi.yml capability_id: BC-4220.30 capability_id_l1: BC-4220 capability_name: Incident Response Management confidence: 0.7 evidence: '"Create a new notification channel"; schemas PagerDutyConfig, IncidentIOConfig, IlertConfig, SlackConfig, NotificationChannelRoutingAsset' reason: Channels route monitoring alerts to on-call tooling (PagerDuty, incident.io, ilert), which is incident detection and on-call coordination. It is not corporate or customer communications; the configuration-only nature of the surface tempers confidence.