Tag: Configuration Issue
Problems related to configuration issues, such as misconfigured settings, invalid parameters, or missing configuration
| ID | Title | Description | Category | Technology | Tags |
|---|---|---|---|---|---|
| prequel-2025-0085 Medium Impact: 7/10 Mitigation: 5/10 | Kafka message size limit exceeded | The Kafka producer encountered a "Message size too large" error when attempting to send a message to a Kafka broker. This occurs when a message exceeds the configured maximum message size limit on the broker. Kafka has configurable message size limits at both broker and producer levels to protect system stability and prevent resource exhaustion. When this limit is hit, the message is rejected and not stored in the topic. | Message Broker Errors | celery | KafkaProducer ErrorConfiguration Issue |
| prequel-2025-0100 Medium Impact: 6/10 Mitigation: 4/10 | Prometheus ingestion failure due to too many labels | Grafana Mimir's distributor rejects incoming Prometheus series when the number of label names on a single series exceeds the configured per-tenant limit. When this occurs, logs contain the message "received a series whose number of labels exceeds the limit" and the affected samples are dropped. This typically arises from excessive or dynamic labeling in scrape targets or relabeling rules that generate many unique label names per series. To adjust the per-tenant limit, configure the distributor with `-validation.max-label-names-per-series`. When deploying via the `mimir-distributed` Helm chart, set `mimir.structuredConfig.limits.max_label_names_per_series` to a higher value (default is 30). Increase limits cautiously to avoid cardinality explosions and memory pressure. Prefer reducing label names at the source where possible. | Observability Problems | distributor | PrometheusGrafanaMetricsConfigurationConfiguration IssueThreshold ExceededObservability |