Tag: Observability
Problems in observability tooling, such as unintended performance impact or missing telemetry
| ID | Title | Description | Category | Technology | Tags |
|---|---|---|---|---|---|
| CRE-2025-0028 Low Impact: 6/10 Mitigation: 1/10 | OpenTelemetry Python fails to detach context token across async boundaries | In OpenTelemetry Python, detaching a context token that was created in a different context can raise a `ValueError`. This occurs when asynchronous operations, such as generators or coroutines, are finalized in a different context than they were created, leading to context management errors and potential trace data loss. | Observability Problems | opentelemetry-python | OpentelemetryPythonContextvarsAsyncObservabilityPublic |
| CRE-2025-0034 Medium Impact: 6/10 Mitigation: 2/10 | Datadog agent disabled due to missing API key | If the Datadog agent or client libraries do not detect a configured API key, they will skip sending metrics, logs, and events. This results in a silent failure of observability reporting, often visible only through startup log messages. | Observability Problems | datadog | DatadogConfigurationApi KeyObservabilityEnvironmentTelemetryKnown IssuePublic |
| CRE-2025-0036 Low Impact: 6/10 Mitigation: 3/10 | OpenTelemetry Collector drops data due to 413 Payload Too Large from exporter target | The OpenTelemetry Collector may drop telemetry data when an exporter backend responds with a 413 Payload Too Large error. This typically happens when large batches of metrics, logs, or traces exceed the maximum payload size accepted by the backend. By default, the collector drops these payloads unless retry behavior is explicitly enabled. | Observability Problems | opentelemetry-collector | Otel CollectorExporterPayloadBatchDropObservabilityTelemetryKnown IssuePublic |
| CRE-2025-0060 Low Impact: 5/10 Mitigation: 2/10 | Datadog OpenMetrics Scrape Returns 404 | - The Datadog Agent is unable to scrape metrics from an OpenMetrics endpoint, returning a 404 Not Found error. - This typically indicates that the target service is either not exposing the `/metrics` path, the port or path is misconfigured, or the service is not running. | Monitoring Problem | datadog | ObservabilityDatadog |
| CRE-2025-0090 Low Impact: 0/10 Mitigation: 0/10 | Loki Log Line Exceeds Max Size Limit | Alloy detects the Loki is dropping log lines because they exceed the configured maximum line size. This typically indicates that applications are emitting extremely long log entries, which Loki is configured to reject by default. | Observability Problems | alloy log | AlloyLokiLogsObservabilityGrafana |