mirror of
https://github.com/krkn-chaos/krkn.git
synced 2026-04-15 06:57:28 +00:00
Naga Ravi Chaitanya Elluri
9858f96c78
This is the first step towards the goal to only have metrics tracking the overall health and performance of the component/cluster. For instance, for etcd disruption scenarios, leader elections are expected, we should instead track etcd leader availability and fsync latency under critical catergory vs leader elections.
12 lines
600 B
Plaintext
12 lines
600 B
Plaintext
- expr: avg_over_time(histogram_quantile(0.99, rate(etcd_disk_wal_fsync_duration_seconds_bucket[2m]))[5m:]) > 0.01
|
|
description: 5 minutes avg. etcd fsync latency on {{$labels.pod}} higher than 10ms {{$value}}
|
|
severity: error
|
|
|
|
- expr: avg_over_time(histogram_quantile(0.99, rate(etcd_network_peer_round_trip_time_seconds_bucket[5m]))[5m:]) > 0.1
|
|
description: 5 minutes avg. etcd netowrk peer round trip on {{$labels.pod}} higher than 100ms {{$value}}
|
|
severity: info
|
|
|
|
- expr: increase(etcd_server_leader_changes_seen_total[2m]) > 0
|
|
description: etcd leader changes observed
|
|
severity: error
|