Observability Pipeline
181 incident problems about Observability Pipeline. Start with the reviewed ones.
먼저 읽을 가이드
추천 문제
All problems (181)
NETWORK-1561An NGINX ingress keeps the new upstream and one site still reports the old client IPOne site logs the wrong client IP after ingress and real_ip cleanup.NetworkAdvanced10 minProK8S-1571A Hubble relay update rolls out and one flow stream still tags the old identityOne Hubble relay still tags the old identity after a Cilium rollout.KubernetesAdvanced11 minProNETWORK-1557A NetFlow exporter migrates and one collector still attributes traffic to the old zoneTraffic is misattributed only after a NetFlow exporter restart and migration.NetworkAdvanced11 minProCICD-1555A canary analysis completes and rollback still misfiresA rollback triggers only in one region after telemetry bucket changes during canary analysis.CI/CDAdvanced12 minProK8S-1473A Prometheus remote-write path stays green and one cluster loses metricsOnly one cluster disappears from storage after external labels are simplified during federation cleanup.KubernetesAdvanced12 minProK8S-1463A Prometheus scrape stays green while custom metrics disappearHPA scaling breaks after two ServiceMonitor definitions are consolidated even though Prometheus still shows the target as healthy.KubernetesAdvanced12 minProK8S-1454A remote-write path looks healthy and one tenant disappearsOne tenant's metrics vanish after exemplars were enabled while overall remote write still reports healthy.KubernetesAdvanced13 minProCICD-1467An Argo Rollouts analysis stays yellowCanary promotions stall right after a metrics label cleanup even though dashboards still show healthy rollout traffic.CI/CDAdvanced13 minProLINUX-1314A journald-backed log pipeline loses structured fieldsA service emits basic startup logs and later operators discover the ongoing structured fields they expected were never forwarded.LinuxAdvanced15 minProLINUX-1304Logrotate appears successful but a high-volume service still loses linesAn application under peak traffic rotates logs cleanly and later operators discover a silent gap around the rotate time.LinuxAdvanced15 minProK8S-1315Loki ingestion is healthy and dashboards are empty for one tenantLoki ingestion is healthy and dashboards are empty for one tenant focuses on Identity And Access and asks the reader to isolate the key signal in grafana. Empty dashboards can be a tenant identity mismatch even when ingestion is healthy.KubernetesAdvanced16 minProK8S-1305Grafana Loki reads logs and still misses new alertsA log platform migrates to object storage and alerting becomes unreliable despite apparently valid credentials and buckets.KubernetesAdvanced17 minProSECURITY-1569A CrowdSec parser is updated and one scenario still missesOne CrowdSec scenario misses events after parser updates.SecurityIntermediate8 minProK8S-1602A custom metrics fix is correct and one HPA still reads zeroOne HPA still reads zero after custom metrics fixes.KubernetesIntermediate8 minProK8S-1592A metrics adapter fix lands and one HPA still stays flatOne HPA still stays flat after metrics adapter corrections.KubernetesIntermediate8 minProSECURITY-1559A CrowdSec parser update lands and one scenario still never firesA response scenario never fires for one firewall feed after parser updates.SecurityIntermediate9 minProLINUX-1579A journald forward path is corrected and one relay still writes duplicatesOne relay writes duplicates after a journald forward path correction.LinuxAdvanced9 minProLINUX-1589A journald forwarder changes and one parser still reads the old hostOne parser still reads the old host after logging standardization.LinuxAdvanced9 minProLINUX-1599A journald relay fix lands and one parser still reads the old hostOne parser still reads the old host after journald relay fixes.LinuxAdvanced9 minProK8S-1582A metrics adapter query is corrected and one HPA still reads zeroOne HPA still reads zero after adapter query corrections.KubernetesIntermediate9 minPro