Prometheus
59 incident problems in Prometheus environments.
먼저 읽을 가이드
추천 문제
All problems (59)
K8S-1512A metrics adapter reports healthy and HPA still does not scaleAn HPA stalls only after scrape interval tuning in the metrics stack.KubernetesIntermediate10 minProK8S-1532A metrics adapter reports healthy and HPA still stays flatAutoscaling stops only after metrics scrape interval tuning.KubernetesIntermediate10 minProK8S-1522A metrics adapter reports healthy and the HPA still stays flatAutoscaling stops only after metrics scrape interval tuning.KubernetesIntermediate10 minProK8S-1562A Prometheus remote-write path backs up and the HPA still reads calm trafficHPA underreacts only when remote-write throttling begins.KubernetesIntermediate10 minProK8S-1502A Prometheus remote-write path drains and one shard still lagsOnly one remote-write shard falls behind after a gateway update changed HTTP header normalization.KubernetesIntermediate10 minProK8S-1492A Prometheus remote-write queue drains and one shard still lagsOnly one remote-write shard keeps falling behind after a gateway change normalized HTTP header casing.KubernetesIntermediate10 minProK8S-1552A Prometheus rule fires and the HPA still idlesAutoscaling stops only for low-volume workloads after recording rule tuning.KubernetesIntermediate10 minProK8S-1482A Prometheus rule reload reports success and one alert stays oldOne shard keeps firing an old alert expression even after a successful Prometheus rule reload.KubernetesIntermediate10 minProK8S-1508An HPA sees demand and never scalesAutoscaling stops after adapter query-step tuning even though Prometheus shows rising demand.KubernetesIntermediate10 minProK8S-1489An HPA sees rising load and refuses to scaleAutoscaling stops only after a deployment rename and metrics adapter refresh that otherwise looks healthy.KubernetesIntermediate10 minProK8S-1498An HPA sees rising metrics and never scalesAutoscaling stops only after query step tuning on the metrics adapter and Prometheus backend.KubernetesIntermediate10 minProK8S-1467A Grafana Agent Flow pipeline duplicates one namespaceOne namespace begins double-counting metrics after a Grafana Agent Flow cleanup merged pod and service discovery blocks.KubernetesIntermediate11 minProK8S-1451An HPA stops scaling from custom metricsCustom metric scaling fails only for one workload after an adapter config reload.KubernetesIntermediate11 minProK8S-1441A PodMonitor stops matching one tenant after a post-render step strips the release label only in that namespaceTargets are healthy, but one rendered namespace no longer satisfies the PodMonitor selector.KubernetesIntermediate11 minProK8S-1421A Prometheus Operator rollout keeps one workload uns scrapedA Prometheus Operator rollout keeps one workload uns scraped focuses on Observability Pipeline and asks the reader to isolate the key signal in Prometheus. Prometheus scraping gaps often come from per-environment render differe...KubernetesIntermediate11 minProK8S-1431A Prometheus Operator upgrade leaves one workload darkOne tenant loses monitoring after a Helm post-renderer rollout while every other namespace continues to scrape correctly.KubernetesIntermediate11 minProK8S-1411A Prometheus scrape target disappears (podmonitor-selector-relied-on-legacy-mirrored-namespace-label)A Prometheus scrape target disappears (podmonitor-selector-relied-on-legacy... focuses on Observability Pipeline and asks the reader to isolate the key signal in Prometheus. Monitoring selectors can depend on label mirroring behav...KubernetesIntermediate11 minProK8S-1401A Prometheus Operator upgrade looks healthy and one ServiceMonitor stops...A Prometheus Operator upgrade looks healthy and one ServiceMonitor stops... focuses on Observability Pipeline and asks the reader to isolate the key signal in Prometheus. Prometheus scraping outages after chart upgrades o...KubernetesIntermediate12 minProK8S-1677An HPA metric is visible and one autoscaler still reads zeroAn autoscaler still reads zero after the metric name was updated.KubernetesIntermediate9 minPro