slug: highlight-io provider: Highlight (highlight.io) 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: highlight-io-logs-api-openapi.yml capability_id: BC-4220.20 capability_id_l1: BC-4220 capability_name: Observability Management confidence: 0.9 evidence: Native OpenTelemetry Protocol (OTLP) HTTP/JSON ingestion endpoint for structured logs ... Logs are stored in ClickHouse for sub-second full-text search reason: OTLP log ingestion for a monitoring platform is squarely observability management (logs, metrics, traces) of the running service. - tag: Traces spec_file: highlight-io-traces-api-openapi.yml capability_id: BC-4220.20 capability_id_l1: BC-4220 capability_name: Observability Management confidence: 0.9 evidence: '"Native OpenTelemetry Protocol (OTLP) HTTP/JSON ingestion endpoint for distributed traces... Spans must carry the `highlight.project_id` resource attribute"' reason: Distributed trace span ingestion is a core observability signal (logs, metrics, traces) for a running SaaS service; no other reading fits. - tag: Metrics spec_file: highlight-io-metrics-api-openapi.yml capability_id: BC-4220.20 capability_id_l1: BC-4220 capability_name: Observability Management confidence: 0.88 evidence: '"Beta OpenTelemetry Protocol (OTLP) HTTP/JSON ingestion endpoint for metrics... Metrics drive Highlight dashboards, monitors, and the metrics SQL editor."' reason: Ingestion of OTLP metrics (gauges, sums, histograms) feeding dashboards and monitors is squarely observability of a running service — logs, metrics, traces. Mapped to Observability Management rather than any business-metric capability.