Observability Pipeline
181 incident problems about Observability Pipeline. Start with the reviewed ones.
먼저 읽을 가이드
추천 문제
All problems (181)
NETWORK-1470A BGP max-prefix alarm never escalatesA peer nearly tears down on max-prefix without the usual alert after a network OS refresh.NetworkIntermediate10 minProNETWORK-1480A BGP session remains up and telemetry still hides a route leakRoute leak indicators are missed because telemetry is grouped at the peer-group level instead of per neighbor.NetworkIntermediate10 minProSECURITY-1494A Falco rule update deploys and one syscall alert keeps firingA single node continues firing a retired Falco alert after a ruleset update across the cluster.SecurityIntermediate10 minProSECURITY-1504A Falco rule update deploys and one syscall alert keeps firingA single node continues firing a retired Falco alert after a ruleset update.SecurityIntermediate10 minProSECURITY-1514A Falco rule update deploys and one syscall alert still firesA single node continues firing a retired Falco alert after a ruleset update.SecurityIntermediate10 minProK8S-1446A Grafana Agent DaemonSet misses one namespaceOne namespace never appears in scrape discovery after a label-controller rollout.KubernetesIntermediate10 minProLINUX-1558A journald forwarder works and one parser still drops linesOnly one relay path drops logs after hostname standardization.LinuxAdvanced10 minProLINUX-1562A journald vacuum completes and one rsyslog relay still drops linesOne rsyslog relay drops lines only after journal vacuum and directory migration.LinuxAdvanced10 minProK8S-1607A Loki rule update is correct and one shard still evaluates old dataOne Loki shard still evaluates old data after a rule update.KubernetesAdvanced10 minProK8S-1587A Loki ruler update is applied and one shard still evaluates the old ruleOne Loki ruler shard evaluates the old rule set after routing updates.KubernetesAdvanced10 minProK8S-1597A Loki tenant split succeeds and one ruler still reads the old OrgIDOne Loki ruler still reads the old OrgID after tenant split.KubernetesAdvanced10 minProK8S-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 minPro