Tag: Grafana
Problems related to Grafana services, that may impact performance, or telemetry collection and storage
| ID | Title | Description | Category | Technology | Tags |
|---|---|---|---|---|---|
| CRE-2025-0019 Low Impact: 3/10 Mitigation: 2/10 | Alloy entries too far behind | Grafana can get into a state where it writes more errors messages than it can process. The problem is compounded when Grafana is collecting its own error logs that include the related warnings that it can no longer keep up. This can consume several GB per day of storage. | Storage | alloy | GrafanaAlloyLokiPublic |
| CRE-2025-0020 Medium Impact: 5/10 Mitigation: 2/10 | Grafana alloy Loki fanout crash | Grafana alloy Loki fanout crashes when the number of log files exceeds the number of ingesters. | Storage | alloy | GrafanaAlloyLokiPublic |
| CRE-2025-0043 Medium Impact: 4/10 Mitigation: 2/10 | Grafana fails to load plugin due to missing signature | Grafana may reject custom or third-party plugins at runtime if they are not digitally signed. When plugin signature validation is enabled (default since Grafana 8+), unsigned plugins are blocked and logged as validation errors during startup or plugin loading. | Observability Problems | grafana | GrafanaPluginValidationSignatureConfigurationSecurityKnown IssuePublic |
| 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 |