ceph/monitoring/ceph-mixin/tests_alerts/test_alerts.yml

2742 lines
122 KiB
YAML

rule_files:
- ../prometheus_alerts.yml
evaluation_interval: 5m
tests:
# health error
- interval: 5m
input_series:
- series: 'ceph_health_status{instance="ceph:9283",job="ceph",cluster="mycluster"}'
values: '2 2 2 2 2 2 2'
promql_expr_test:
- expr: ceph_health_status == 2
eval_time: 5m
exp_samples:
- labels: 'ceph_health_status{instance="ceph:9283",job="ceph",cluster="mycluster"}'
value: 2
alert_rule_test:
- eval_time: 1m
alertname: CephHealthError
- eval_time: 6m
alertname: CephHealthError
exp_alerts:
- exp_labels:
instance: ceph:9283
job: ceph
oid: 1.3.6.1.4.1.50495.1.2.1.2.1
type: ceph_default
severity: critical
cluster: mycluster
exp_annotations:
summary: Ceph is in the ERROR state on cluster mycluster
description: The cluster state has been HEALTH_ERROR for more than 5 minutes on cluster mycluster. Please check 'ceph health detail' for more information.
# health warning
- interval: 5m
input_series:
- series: 'ceph_health_status{instance="ceph:9283",job="ceph",cluster="mycluster"}'
values: '1 1 1 1 1 1 1 1 1 1'
promql_expr_test:
- expr: ceph_health_status == 1
eval_time: 15m
exp_samples:
- labels: 'ceph_health_status{instance="ceph:9283",job="ceph",cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 10m
alertname: CephHealthWarning
- eval_time: 20m
alertname: CephHealthWarning
exp_alerts:
- exp_labels:
instance: ceph:9283
job: ceph
type: ceph_default
severity: warning
cluster: mycluster
exp_annotations:
summary: Ceph is in the WARNING state on cluster mycluster
description: The cluster state has been HEALTH_WARN for more than 15 minutes on cluster mycluster. Please check 'ceph health detail' for more information.
# 10% OSDs down
- interval: 1m
input_series:
- series: 'ceph_osd_up{ceph_daemon="osd.0",instance="ceph:9283",job="ceph",cluster="mycluster"}'
values: '1 1 1 1 1'
- series: 'ceph_osd_up{ceph_daemon="osd.1",instance="ceph:9283",job="ceph",cluster="mycluster"}'
values: '0 0 0 0 0'
- series: 'ceph_osd_up{ceph_daemon="osd.2",instance="ceph:9283",job="ceph",cluster="mycluster"}'
values: '1 1 1 1 1'
- series: 'ceph_osd_metadata{back_iface="eth0",ceph_daemon="osd.0",
ceph_version="ceph version 17.0.0-189-g3558fd72
(3558fd7291855971aa6481a2ade468ad61fbb346) pacific (dev)",
cluster_addr="172.20.0.2",device_class="hdd",front_iface="eth0",
hostname="ceph",instance="ceph:9283",job="ceph",cluster="mycluster",objectstore="bluestore",
public_addr="172.20.0.2"}'
values: '1 1 1 1 1'
- series: 'ceph_osd_metadata{back_iface="eth0",ceph_daemon="osd.1",
ceph_version="ceph version 17.0.0-189-g3558fd72
(3558fd7291855971aa6481a2ade468ad61fbb346) pacific (dev)",
cluster_addr="172.20.0.2",device_class="hdd",front_iface="eth0",
hostname="ceph",instance="ceph:9283",job="ceph",cluster="mycluster",objectstore="bluestore",
public_addr="172.20.0.2"}'
values: '1 1 1 1 1'
- series: 'ceph_osd_metadata{back_iface="eth0",ceph_daemon="osd.2",
ceph_version="ceph version 17.0.0-189-g3558fd72
(3558fd7291855971aa6481a2ade468ad61fbb346) pacific (dev)",
cluster_addr="172.20.0.2",device_class="hdd",front_iface="eth0",
hostname="ceph",instance="ceph:9283",job="ceph",cluster="mycluster",objectstore="bluestore",
public_addr="172.20.0.2"}'
values: '1 1 1 1 1'
promql_expr_test:
- expr: count by (cluster) (ceph_osd_up == 0) / count by (cluster) (ceph_osd_up) * 100 >= 10
eval_time: 1m
exp_samples:
- labels: '{cluster="mycluster" }'
value: 3.333333333333333E+01
alert_rule_test:
- eval_time: 1m
alertname: CephOSDDownHigh
exp_alerts:
- exp_labels:
oid: 1.3.6.1.4.1.50495.1.2.1.4.1
type: ceph_default
severity: critical
cluster: mycluster
exp_annotations:
summary: More than 10% of OSDs are down on cluster mycluster
description: "33.33% or 1 of 3 OSDs are down (>= 10%). The following OSDs are down: - osd.1 on ceph"
# flapping OSD
- interval: 1s
input_series:
- series: 'ceph_osd_up{ceph_daemon="osd.0",instance="ceph:9283",job="ceph",cluster="mycluster"}'
values: '1+1x100'
- series: 'ceph_osd_up{ceph_daemon="osd.1",instance="ceph:9283",job="ceph",cluster="mycluster"}'
values: '1+0x100'
- series: 'ceph_osd_up{ceph_daemon="osd.2",instance="ceph:9283",job="ceph",cluster="mycluster"}'
values: '1+0x100'
- series: 'ceph_osd_metadata{back_iface="eth0",ceph_daemon="osd.0",
ceph_version="ceph version 17.0.0-189-g3558fd72
(3558fd7291855971aa6481a2ade468ad61fbb346) pacific (dev)",
cluster_addr="172.20.0.2",device_class="hdd",front_iface="eth0",
hostname="ceph",instance="ceph:9283",job="ceph",objectstore="bluestore",
public_addr="172.20.0.2",cluster="mycluster"}'
values: '1 1 1 1 1 1'
- series: 'ceph_osd_metadata{back_iface="eth0",ceph_daemon="osd.1",
ceph_version="ceph version 17.0.0-189-g3558fd72
(3558fd7291855971aa6481a2ade468ad61fbb346) pacific (dev)",
cluster_addr="172.20.0.2",device_class="hdd",front_iface="eth0",
hostname="ceph",instance="ceph:9283",job="ceph",objectstore="bluestore",
public_addr="172.20.0.2",cluster="mycluster"}'
values: '1 1 1 1 1 1'
- series: 'ceph_osd_metadata{back_iface="eth0",ceph_daemon="osd.2",
ceph_version="ceph version 17.0.0-189-g3558fd72
(3558fd7291855971aa6481a2ade468ad61fbb346) pacific (dev)",
cluster_addr="172.20.0.2",device_class="hdd",front_iface="eth0",
hostname="ceph",instance="ceph:9283",job="ceph",objectstore="bluestore",
public_addr="172.20.0.2",cluster="mycluster"}'
values: '1 1 1 1 1 1'
promql_expr_test:
- expr: |
(
rate(ceph_osd_up[5m])
* on(ceph_daemon) group_left(hostname) ceph_osd_metadata
) * 60 > 1
eval_time: 1m
exp_samples:
- labels: '{ceph_daemon="osd.0", hostname="ceph", instance="ceph:9283",
job="ceph",cluster="mycluster"}'
value: 1.2200000000000001E+01
alert_rule_test:
- eval_time: 5m
alertname: CephOSDFlapping
exp_alerts:
- exp_labels:
ceph_daemon: osd.0
hostname: ceph
instance: ceph:9283
job: ceph
oid: 1.3.6.1.4.1.50495.1.2.1.4.4
severity: warning
cluster: mycluster
type: ceph_default
exp_annotations:
documentation: https://docs.ceph.com/en/latest/rados/troubleshooting/troubleshooting-osd#flapping-osds
summary: Network issues are causing OSDs to flap (mark each other down) on cluster mycluster
description: "OSD osd.0 on ceph was marked down and back up 20.1 times once a minute for 5 minutes. This may indicate a network issue (latency, packet loss, MTU mismatch) on the cluster network, or the public network if no cluster network is deployed. Check the network stats on the listed host(s)."
# high pg count deviation
- interval: 1m
input_series:
- series: 'ceph_osd_numpg{ceph_daemon="osd.0",instance="ceph:9283",job="ceph",cluster="mycluster"}'
values: '100 100 100 100 100 160'
- series: 'ceph_osd_numpg{ceph_daemon="osd.1",instance="ceph:9283",job="ceph",cluster="mycluster"}'
values: '100 100 100 100 100 320'
- series: 'ceph_osd_numpg{ceph_daemon="osd.2",instance="ceph:9283",job="ceph",cluster="mycluster"}'
values: '100 100 100 100 100 160'
- series: 'ceph_osd_numpg{ceph_daemon="osd.3",instance="ceph:9283",job="ceph",cluster="mycluster"}'
values: '100 100 100 100 100 160'
- series: 'ceph_osd_metadata{back_iface="eth0",ceph_daemon="osd.0",ceph_version="ceph version 17.0.0-189-g3558fd72
(3558fd7291855971aa6481a2ade468ad61fbb346) pacific (dev)",cluster_addr="172.20.0.2",device_class="hdd",front_iface="eth0",
hostname="ceph",instance="ceph:9283",job="ceph",objectstore="bluestore",public_addr="172.20.0.2",cluster="mycluster"}'
values: '1 1 1 1 1 1'
- series: 'ceph_osd_metadata{back_iface="eth0",ceph_daemon="osd.1",ceph_version="ceph version 17.0.0-189-g3558fd72
(3558fd7291855971aa6481a2ade468ad61fbb346) pacific (dev)",cluster_addr="172.20.0.2",device_class="hdd",front_iface="eth0",
hostname="ceph",instance="ceph:9283",job="ceph",objectstore="bluestore",public_addr="172.20.0.2",cluster="mycluster"}'
values: '1 1 1 1 1 1'
- series: 'ceph_osd_metadata{back_iface="eth0",ceph_daemon="osd.2",ceph_version="ceph version 17.0.0-189-g3558fd72
(3558fd7291855971aa6481a2ade468ad61fbb346) pacific (dev)",cluster_addr="172.20.0.2",device_class="hdd",front_iface="eth0",
hostname="ceph",instance="ceph:9283",job="ceph",objectstore="bluestore",public_addr="172.20.0.2",cluster="mycluster"}'
values: '1 1 1 1 1 1'
- series: 'ceph_osd_metadata{back_iface="eth0",ceph_daemon="osd.3",ceph_version="ceph version 17.0.0-189-g3558fd72
(3558fd7291855971aa6481a2ade468ad61fbb346) pacific (dev)",cluster_addr="172.20.0.2",device_class="hdd",front_iface="eth0",
hostname="ceph",instance="ceph:9283",job="ceph",objectstore="bluestore",public_addr="172.20.0.2",cluster="mycluster"}'
values: '1 1 1 1 1 1'
promql_expr_test:
- expr: |
abs(
(
(ceph_osd_numpg > 0) - on (job) group_left avg(ceph_osd_numpg > 0)
by (job)
) / on (job) group_left avg(ceph_osd_numpg > 0) by (job)
) * on(ceph_daemon) group_left(hostname) ceph_osd_metadata > 0.30
eval_time: 5m
exp_samples:
- labels: '{ceph_daemon="osd.1", hostname="ceph", instance="ceph:9283",job="ceph",cluster="mycluster"}'
value: 6E-01
alert_rule_test:
- eval_time: 10m
alertname: CephPGImbalance
exp_alerts:
- exp_labels:
ceph_daemon: osd.1
hostname: ceph
instance: ceph:9283
job: ceph
oid: 1.3.6.1.4.1.50495.1.2.1.4.5
severity: warning
cluster: mycluster
type: ceph_default
exp_annotations:
summary: PGs are not balanced across OSDs on cluster mycluster
description: "OSD osd.1 on ceph deviates by more than 30% from average PG count."
# pgs inactive
- interval: 1m
input_series:
- series: 'ceph_pool_metadata{instance="ceph:9283",job="ceph",cluster="mycluster",name="device_health_metrics",pool_id="1"}'
values: '1 1 1 1 1 1 1 1'
- series: 'ceph_pool_metadata{instance="ceph:9283",job="ceph",cluster="mycluster",name="device_health_metrics",pool_id="2"}'
values: '1 1 1 1 1 1 1 1'
- series: 'ceph_pool_metadata{instance="ceph:9283",job="ceph",cluster="mycluster",name="device_health_metrics",pool_id="3"}'
values: '1 1 1 1 1 1 1 1'
- series: 'ceph_pg_total{instance="ceph:9283",job="ceph",cluster="mycluster",pool_id="1"}'
values: '1 1 1 1 1 1 1 1'
- series: 'ceph_pg_total{instance="ceph:9283",job="ceph",cluster="mycluster",pool_id="2"}'
values: '32 32 32 32 32 32 32 32'
- series: 'ceph_pg_total{instance="ceph:9283",job="ceph",cluster="mycluster",pool_id="3"}'
values: '33 32 32 32 32 33 33 32'
- series: 'ceph_pg_active{instance="ceph:9283",job="ceph",cluster="mycluster",pool_id="1"}'
values: '1 1 1 1 1 1 1 1 1'
- series: 'ceph_pg_active{instance="ceph:9283",job="ceph",cluster="mycluster",pool_id="2"}'
values: '32 32 32 32 32 32 32 32'
- series: 'ceph_pg_active{instance="ceph:9283",job="ceph",cluster="mycluster",pool_id="3"}'
values: '32 32 32 32 32 32 32 32'
promql_expr_test:
- expr: ceph_pool_metadata * on(pool_id,instance) group_left()
(ceph_pg_total - ceph_pg_active) > 0
eval_time: 5m
exp_samples:
- labels: '{instance="ceph:9283", job="ceph",cluster="mycluster",name="device_health_metrics",pool_id="3"}'
value: 1
alert_rule_test:
- eval_time: 5m
alertname: CephPGsInactive
exp_alerts:
- exp_labels:
instance: ceph:9283
job: ceph
name: device_health_metrics
oid: 1.3.6.1.4.1.50495.1.2.1.7.1
pool_id: 3
severity: critical
cluster: mycluster
type: ceph_default
exp_annotations:
summary: One or more placement groups are inactive on cluster mycluster
description: "1 PGs have been inactive for more than 5 minutes in pool device_health_metrics. Inactive placement groups are not able to serve read/write requests."
#pgs unclean
- interval: 1m
input_series:
- series: 'ceph_pool_metadata{instance="ceph:9283",job="ceph",cluster="mycluster",name="device_health_metrics",pool_id="1"}'
values: '1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1'
- series: 'ceph_pool_metadata{instance="ceph:9283",job="ceph",cluster="mycluster",name="device_health_metrics",pool_id="2"}'
values: '1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1'
- series: 'ceph_pool_metadata{instance="ceph:9283",job="ceph",cluster="mycluster",name="device_health_metrics",pool_id="3"}'
values: '1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1'
- series: 'ceph_pg_total{instance="ceph:9283",job="ceph",cluster="mycluster",pool_id="1"}'
values: '1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1'
- series: 'ceph_pg_total{instance="ceph:9283",job="ceph",cluster="mycluster",pool_id="2"}'
values: '32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32'
- series: 'ceph_pg_total{instance="ceph:9283",job="ceph",cluster="mycluster",pool_id="3"}'
values: '33 33 33 33 33 33 33 33 33 33 33 33 33 33 33 33 33 33 33 33 33 33 33'
- series: 'ceph_pg_clean{instance="ceph:9283",job="ceph",cluster="mycluster",pool_id="1"}'
values: '1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1'
- series: 'ceph_pg_clean{instance="ceph:9283",job="ceph",cluster="mycluster",pool_id="2"}'
values: '32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32'
- series: 'ceph_pg_clean{instance="ceph:9283",job="ceph",cluster="mycluster",pool_id="3"}'
values: '32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32'
promql_expr_test:
- expr: ceph_pool_metadata * on(pool_id,instance) group_left()
(ceph_pg_total - ceph_pg_clean) > 0
eval_time: 15m
exp_samples:
- labels: '{instance="ceph:9283", job="ceph",cluster="mycluster",name="device_health_metrics", pool_id="3"}'
value: 1
alert_rule_test:
- eval_time: 16m
alertname: CephPGsUnclean
exp_alerts:
- exp_labels:
instance: ceph:9283
job: ceph
name: device_health_metrics
oid: 1.3.6.1.4.1.50495.1.2.1.7.2
pool_id: 3
severity: warning
cluster: mycluster
type: ceph_default
exp_annotations:
summary: One or more placement groups are marked unclean on cluster mycluster
description: "1 PGs have been unclean for more than 15 minutes in pool device_health_metrics. Unclean PGs have not recovered from a previous failure."
# root volume full
- interval: 1m
input_series:
- series: 'node_filesystem_avail_bytes{device="/dev/mapper/fedora_localhost
--live-home",fstype="ext4",instance="node-exporter",job="node-exporter",
mountpoint="/"}'
values: '35336400896 35336400896 35336400896 35336400896 35336400896
3525385519.104 3533640089'
- series: 'node_filesystem_size_bytes{device="/dev/mapper/fedora_localhost
--live-home",fstype="ext4",instance="node-exporter",job="node-exporter",
mountpoint="/"}'
values: '73445531648 73445531648 73445531648 73445531648 73445531648
73445531648 73445531648'
promql_expr_test:
- expr: node_filesystem_avail_bytes{mountpoint="/"} /
node_filesystem_size_bytes{mountpoint="/"} * 100 < 5
eval_time: 5m
exp_samples:
- labels: '{device="/dev/mapper/fedora_localhost --live-home",
fstype="ext4", instance="node-exporter", job="node-exporter",
mountpoint="/"}'
value: 4.8E+00
alert_rule_test:
- eval_time: 10m
alertname: CephNodeRootFilesystemFull
exp_alerts:
- exp_labels:
device: /dev/mapper/fedora_localhost --live-home
fstype: ext4
instance: node-exporter
job: node-exporter
mountpoint: /
oid: 1.3.6.1.4.1.50495.1.2.1.8.1
severity: critical
type: ceph_default
exp_annotations:
summary: Root filesystem is dangerously full
description: "Root volume is dangerously full: 4.811% free."
# network packets dropped
- interval: 1m
input_series:
- series: 'node_network_receive_drop_total{device="eth0",instance="node-exporter",job="node-exporter"}'
values: '0+600x10'
- series: 'node_network_transmit_drop_total{device="eth0",instance="node-exporter",job="node-exporter"}'
values: '0+600x10'
- series: 'node_network_receive_packets_total{device="eth0",instance="node-exporter",job="node-exporter"}'
values: '0+750x10'
- series: 'node_network_transmit_packets_total{device="eth0",instance="node-exporter",job="node-exporter"}'
values: '0+750x10'
promql_expr_test:
- expr: |
(
rate(node_network_receive_drop_total{device!="lo"}[1m]) +
rate(node_network_transmit_drop_total{device!="lo"}[1m])
) / (
rate(node_network_receive_packets_total{device!="lo"}[1m]) +
rate(node_network_transmit_packets_total{device!="lo"}[1m])
) >= 0.0050000000000000001 and (
rate(node_network_receive_drop_total{device!="lo"}[1m]) +
rate(node_network_transmit_drop_total{device!="lo"}[1m])
) >= 10
eval_time: 5m
exp_samples:
- labels: '{device="eth0", instance="node-exporter",job="node-exporter"}'
value: 8E-1
alert_rule_test:
- eval_time: 5m
alertname: CephNodeNetworkPacketDrops
exp_alerts:
- exp_labels:
device: eth0
instance: node-exporter
job: node-exporter
oid: 1.3.6.1.4.1.50495.1.2.1.8.2
severity: warning
type: ceph_default
exp_annotations:
summary: One or more NICs reports packet drops
description: "Node node-exporter experiences packet drop > 0.5% or > 10 packets/s on interface eth0."
# network packets errors
- interval: 1m
input_series:
- series: 'node_network_receive_errs_total{device="eth0",instance="node-exporter",job="node-exporter",cluster="mycluster"}'
values: '0+600x10'
- series: 'node_network_transmit_errs_total{device="eth0",instance="node-exporter",job="node-exporter",cluster="mycluster"}'
values: '0+600x10'
- series: 'node_network_transmit_packets_total{device="eth0",instance="node-exporter",job="node-exporter",cluster="mycluster"}'
values: '0+750x10'
- series: 'node_network_receive_packets_total{device="eth0",instance="node-exporter",job="node-exporter",cluster="mycluster"}'
values: '0+750x10'
promql_expr_test:
- expr: |
(
rate(node_network_receive_errs_total{device!="lo"}[1m]) +
rate(node_network_transmit_errs_total{device!="lo"}[1m])
) / (
rate(node_network_receive_packets_total{device!="lo"}[1m]) +
rate(node_network_transmit_packets_total{device!="lo"}[1m])
) >= 0.0001 or (
rate(node_network_receive_errs_total{device!="lo"}[1m]) +
rate(node_network_transmit_errs_total{device!="lo"}[1m])
) >= 10
eval_time: 5m
exp_samples:
- labels: '{device="eth0", instance="node-exporter",job="node-exporter",cluster="mycluster"}'
value: 8E-01
alert_rule_test:
- eval_time: 5m
alertname: CephNodeNetworkPacketErrors
exp_alerts:
- exp_labels:
device: eth0
instance: node-exporter
job: node-exporter
oid: 1.3.6.1.4.1.50495.1.2.1.8.3
severity: warning
type: ceph_default
cluster: mycluster
exp_annotations:
summary: One or more NICs reports packet errors on cluster mycluster
description: "Node node-exporter experiences packet errors > 0.01% or > 10 packets/s on interface eth0."
# Bond is missing a peer
- interval: 1m
input_series:
- series: 'node_bonding_active{master="bond0",instance="node-exporter",job="node-exporter",cluster="mycluster"}'
values: '3'
- series: 'node_bonding_slaves{master="bond0",instance="node-exporter",job="node-exporter",cluster="mycluster"}'
values: '4'
promql_expr_test:
- expr: |
node_bonding_slaves - node_bonding_active != 0
eval_time: 5m
exp_samples:
- labels: '{master="bond0", instance="node-exporter",job="node-exporter",cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 5m
alertname: CephNodeNetworkBondDegraded
exp_alerts:
- exp_labels:
master: bond0
instance: node-exporter
job: node-exporter
severity: warning
type: ceph_default
cluster: mycluster
exp_annotations:
summary: Degraded Bond on Node node-exporter on cluster mycluster
description: "Bond bond0 is degraded on Node node-exporter."
# Node Storage disk space filling up
- interval: 1m
# 20GB = 21474836480, 256MB = 268435456
input_series:
- series: 'node_filesystem_free_bytes{device="/dev/mapper/vg-root",fstype="xfs",instance="node-1",mountpoint="/rootfs",cluster="mycluster"}'
values: '21474836480-268435456x48'
- series: 'node_filesystem_free_bytes{device="/dev/mapper/vg-root",fstype="xfs",instance="node-2",mountpoint="/rootfs",cluster="mycluster"}'
values: '21474836480+0x48'
- series: 'node_uname_info{instance="node-1", nodename="node-1.unittests.com",cluster="mycluster"}'
values: 1+0x48
- series: 'node_uname_info{instance="node-2", nodename="node-2.unittests.com",cluster="mycluster"}'
values: 1+0x48
promql_expr_test:
- expr: |
predict_linear(node_filesystem_free_bytes{device=~"/.*"}[2d], 3600 * 24 * 5) *
on(instance) group_left(nodename) node_uname_info < 0
eval_time: 5m
exp_samples:
- labels: '{device="/dev/mapper/vg-root",instance="node-1",fstype="xfs",mountpoint="/rootfs",nodename="node-1.unittests.com",cluster="mycluster"}'
value: -1.912602624E+12
alert_rule_test:
- eval_time: 5m
alertname: CephNodeDiskspaceWarning
exp_alerts:
- exp_labels:
severity: warning
type: ceph_default
oid: 1.3.6.1.4.1.50495.1.2.1.8.4
device: /dev/mapper/vg-root
fstype: xfs
instance: node-1
mountpoint: /rootfs
nodename: node-1.unittests.com
cluster: mycluster
exp_annotations:
summary: Host filesystem free space is getting low on cluster mycluster
description: "Mountpoint /rootfs on node-1.unittests.com will be full in less than 5 days based on the 48 hour trailing fill rate."
# MTU Mismatch
- interval: 1m
input_series:
- series: 'node_network_mtu_bytes{device="eth0",instance="node-exporter",job="node-exporter",cluster="mycluster"}'
values: '1500 1500 1500 1500 1500'
- series: 'node_network_mtu_bytes{device="eth1",instance="node-exporter",job="node-exporter",cluster="mycluster"}'
values: '1500 1500 1500 1500 1500'
- series: 'node_network_mtu_bytes{device="eth2",instance="node-exporter",job="node-exporter",cluster="mycluster"}'
values: '1500 1500 1500 1500 1500'
- series: 'node_network_mtu_bytes{device="eth3",instance="node-exporter",job="node-exporter",cluster="mycluster"}'
values: '1500 1500 1500 1500 1500'
- series: 'node_network_mtu_bytes{device="eth4",instance="node-exporter",job="node-exporter",cluster="mycluster"}'
values: '9000 9000 9000 9000 9000'
- series: 'node_network_mtu_bytes{device="eth4",instance="hostname1",job="node-exporter",cluster="mycluster"}'
values: '2200 2200 2200 2200 2200'
- series: 'node_network_mtu_bytes{device="eth4",instance="hostname2",job="node-exporter",cluster="mycluster"}'
values: '2400 2400 2400 2400 2400'
- series: 'node_network_up{device="eth0",instance="node-exporter",job="node-exporter",cluster="mycluster"}'
values: '0 0 0 0 0'
- series: 'node_network_up{device="eth1",instance="node-exporter",job="node-exporter",cluster="mycluster"}'
values: '0 0 0 0 0'
- series: 'node_network_up{device="eth2",instance="node-exporter",job="node-exporter",cluster="mycluster"}'
values: '1 1 1 1 1'
- series: 'node_network_up{device="eth3",instance="node-exporter",job="node-exporter",cluster="mycluster"}'
values: '1 1 1 1 1'
- series: 'node_network_up{device="eth4",instance="node-exporter",job="node-exporter",cluster="mycluster"}'
values: '1 1 1 1 1'
- series: 'node_network_up{device="eth4",instance="hostname1",job="node-exporter",cluster="mycluster"}'
values: '1 1 1 1 1'
- series: 'node_network_up{device="eth4",instance="hostname2",job="node-exporter",cluster="mycluster"}'
values: '0 0 0 0 0'
promql_expr_test:
- expr: |
node_network_mtu_bytes * (node_network_up{device!="lo"} > 0) ==
scalar(
max by (cluster,device) (node_network_mtu_bytes * (node_network_up{device!="lo"} > 0)) !=
quantile by (cluster,device) (.5, node_network_mtu_bytes * (node_network_up{device!="lo"} > 0))
)
or
node_network_mtu_bytes * (node_network_up{device!="lo"} > 0) ==
scalar(
min by (cluster,device) (node_network_mtu_bytes * (node_network_up{device!="lo"} > 0)) !=
quantile by (cluster,device) (.5, node_network_mtu_bytes * (node_network_up{device!="lo"} > 0))
)
eval_time: 1m
exp_samples:
- labels: '{device="eth4", instance="node-exporter", job="node-exporter", cluster="mycluster"}'
value: 9000
- labels: '{device="eth4", instance="hostname1", job="node-exporter", cluster="mycluster"}'
value: 2200
alert_rule_test:
- eval_time: 1m
alertname: CephNodeInconsistentMTU
exp_alerts:
- exp_labels:
device: eth4
instance: hostname1
job: node-exporter
severity: warning
type: ceph_default
cluster: "mycluster"
exp_annotations:
summary: MTU settings across Ceph hosts are inconsistent on cluster mycluster
description: "Node hostname1 has a different MTU size (2200) than the median of devices named eth4."
- exp_labels:
device: eth4
instance: node-exporter
job: node-exporter
severity: warning
type: ceph_default
cluster: "mycluster"
exp_annotations:
summary: MTU settings across Ceph hosts are inconsistent on cluster mycluster
description: "Node node-exporter has a different MTU size (9000) than the median of devices named eth4."
# pool full, data series has 6 but using topk(5) so to ensure the
# results are working as expected
- interval: 1m
input_series:
- series: 'ceph_health_detail{name="POOL_FULL", cluster="mycluster"}'
values: '0 0 0 1 1 1 1 1 1 1 1'
- series: 'ceph_pool_percent_used{pool_id="1", cluster="mycluster"}'
values: '32+0x10'
- series: 'ceph_pool_percent_used{pool_id="2", cluster="mycluster"}'
values: '96+0x10'
- series: 'ceph_pool_percent_used{pool_id="3", cluster="mycluster"}'
values: '90+0x10'
- series: 'ceph_pool_percent_used{pool_id="4", cluster="mycluster"}'
values: '72+0x10'
- series: 'ceph_pool_percent_used{pool_id="5", cluster="mycluster"}'
values: '19+0x10'
- series: 'ceph_pool_percent_used{pool_id="6", cluster="mycluster"}'
values: '10+0x10'
- series: 'ceph_pool_metadata{instance="ceph:9283",job="ceph",
name="cephfs_data",pool_id="1", cluster="mycluster"}'
values: '1 1 1 1 1 1 1 1 1'
- series: 'ceph_pool_metadata{instance="ceph:9283",job="ceph",
name="rbd",pool_id="2", cluster="mycluster"}'
values: '1 1 1 1 1 1 1 1 1'
- series: 'ceph_pool_metadata{instance="ceph:9283",job="ceph",
name="iscsi",pool_id="3", cluster="mycluster"}'
values: '1 1 1 1 1 1 1 1 1'
- series: 'ceph_pool_metadata{instance="ceph:9283",job="ceph",
name="default.rgw.index",pool_id="4", cluster="mycluster"}'
values: '1 1 1 1 1 1 1 1 1'
- series: 'ceph_pool_metadata{instance="ceph:9283",job="ceph",
name="default.rgw.log",pool_id="5", cluster="mycluster"}'
values: '1 1 1 1 1 1 1 1 1'
- series: 'ceph_pool_metadata{instance="ceph:9283",job="ceph",
name="dummy",pool_id="6", cluster="mycluster"}'
values: '1 1 1 1 1 1 1 1 1'
promql_expr_test:
- expr: ceph_health_detail{name="POOL_FULL"} > 0
eval_time: 5m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="POOL_FULL", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 1m
alertname: CephPoolFull
- eval_time: 10m
alertname: CephPoolFull
exp_alerts:
- exp_labels:
name: POOL_FULL
severity: critical
cluster: mycluster
type: ceph_default
oid: 1.3.6.1.4.1.50495.1.2.1.9.1
exp_annotations:
documentation: https://docs.ceph.com/en/latest/rados/operations/health-checks#pool-full
summary: Pool is full - writes are blocked on cluster mycluster
description: "A pool has reached its MAX quota, or OSDs supporting the pool have reached the FULL threshold. Until this is resolved, writes to the pool will be blocked. Pool Breakdown (top 5) - rbd at 96% - iscsi at 90% - default.rgw.index at 72% - cephfs_data at 32% - default.rgw.log at 19% Increase the pool's quota, or add capacity to the cluster first then increase the pool's quota (e.g. ceph osd pool set quota <pool_name> max_bytes <bytes>)"
# slow OSD ops
- interval : 1m
input_series:
- series: 'ceph_healthcheck_slow_ops{instance="ceph:9283",job="ceph",cluster="mycluster"}'
values: '1+0x120'
promql_expr_test:
- expr: ceph_healthcheck_slow_ops > 0
eval_time: 1m
exp_samples:
- labels: '{__name__="ceph_healthcheck_slow_ops", instance="ceph:9283",job="ceph",cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 20m
alertname: CephSlowOps
exp_alerts:
- exp_labels:
instance: ceph:9283
job: ceph
severity: warning
cluster: mycluster
type: ceph_default
exp_annotations:
documentation: https://docs.ceph.com/en/latest/rados/operations/health-checks#slow-ops
summary: OSD operations are slow to complete on cluster mycluster
description: "1 OSD requests are taking too long to process (osd_op_complaint_time exceeded)"
# slow daemon ops
- interval : 1m
input_series:
- series: 'ceph_daemon_health_metrics{ceph_daemon="osd.1", instance="ceph:9283", job="ceph", type="SLOW_OPS", cluster="mycluster"}'
values: '1+0x120'
promql_expr_test:
- expr: 'ceph_daemon_health_metrics{type="SLOW_OPS"} > 0'
eval_time: 1m
exp_samples:
- labels: '{__name__="ceph_daemon_health_metrics", ceph_daemon="osd.1", instance="ceph:9283", cluster="mycluster",job="ceph", type="SLOW_OPS"}'
value: 1
alert_rule_test:
- eval_time: 20m
alertname: CephDaemonSlowOps
exp_alerts:
- exp_labels:
instance: ceph:9283
ceph_daemon: "osd.1"
job: ceph
severity: warning
cluster: mycluster
type: ceph_default
exp_annotations:
documentation: https://docs.ceph.com/en/latest/rados/operations/health-checks#slow-ops
summary: osd.1 operations are slow to complete on cluster mycluster
description: "osd.1 operations are taking too long to process (complaint time exceeded)"
# CEPHADM orchestrator alert triggers
- interval: 30s
input_series:
- series: 'ceph_health_detail{name="UPGRADE_EXCEPTION", cluster="mycluster"}'
values: '1+0x40'
promql_expr_test:
- expr: ceph_health_detail{name="UPGRADE_EXCEPTION"} > 0
eval_time: 2m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="UPGRADE_EXCEPTION", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 1m
alertname: CephadmUpgradeFailed
- eval_time: 5m
alertname: CephadmUpgradeFailed
exp_alerts:
- exp_labels:
name: UPGRADE_EXCEPTION
severity: critical
cluster: mycluster
type: ceph_default
oid: 1.3.6.1.4.1.50495.1.2.1.11.2
exp_annotations:
summary: Ceph version upgrade has failed on cluster mycluster
description: "The cephadm cluster upgrade process has failed. The cluster remains in an undetermined state. Please review the cephadm logs, to understand the nature of the issue"
- interval: 30s
input_series:
- series: 'ceph_health_detail{name="CEPHADM_FAILED_DAEMON", cluster="mycluster"}'
values: '1+0x40'
promql_expr_test:
- expr: ceph_health_detail{name="CEPHADM_FAILED_DAEMON"} > 0
eval_time: 2m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="CEPHADM_FAILED_DAEMON", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 1m
alertname: CephadmDaemonFailed
- eval_time: 5m
alertname: CephadmDaemonFailed
exp_alerts:
- exp_labels:
name: CEPHADM_FAILED_DAEMON
severity: critical
cluster: mycluster
type: ceph_default
oid: 1.3.6.1.4.1.50495.1.2.1.11.1
exp_annotations:
summary: A ceph daemon managed by cephadm is down on cluster mycluster
description: "A daemon managed by cephadm is no longer active. Determine, which daemon is down with 'ceph health detail'. you may start daemons with the 'ceph orch daemon start <daemon_id>'"
- interval: 1m
input_series:
- series: 'ceph_health_detail{name="CEPHADM_PAUSED", cluster="mycluster"}'
values: '1 1 1 1 1 1 1 1 1'
promql_expr_test:
- expr: ceph_health_detail{name="CEPHADM_PAUSED"} > 0
eval_time: 2m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="CEPHADM_PAUSED", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 1m
alertname: CephadmPaused
- eval_time: 5m
alertname: CephadmPaused
exp_alerts:
- exp_labels:
name: CEPHADM_PAUSED
severity: warning
cluster: mycluster
type: ceph_default
exp_annotations:
documentation: https://docs.ceph.com/en/latest/cephadm/operations#cephadm-paused
summary: Orchestration tasks via cephadm are PAUSED on cluster mycluster
description: "Cluster management has been paused manually. This will prevent the orchestrator from service management and reconciliation. If this is not intentional, resume cephadm operations with 'ceph orch resume'"
# MDS
- interval: 1m
input_series:
- series: 'ceph_health_detail{name="MDS_DAMAGE", cluster="mycluster"}'
values: '1 1 1 1 1 1 1 1 1'
promql_expr_test:
- expr: ceph_health_detail{name="MDS_DAMAGE"} > 0
eval_time: 2m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="MDS_DAMAGE", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 1m
alertname: CephFilesystemDamaged
- eval_time: 5m
alertname: CephFilesystemDamaged
exp_alerts:
- exp_labels:
name: MDS_DAMAGE
severity: critical
cluster: mycluster
type: ceph_default
oid: 1.3.6.1.4.1.50495.1.2.1.5.1
exp_annotations:
documentation: https://docs.ceph.com/en/latest/cephfs/health-messages#cephfs-health-messages
summary: CephFS filesystem is damaged on cluster mycluster
description: "Filesystem metadata has been corrupted. Data may be inaccessible. Analyze metrics from the MDS daemon admin socket, or escalate to support."
- interval: 1m
input_series:
- series: 'ceph_health_detail{name="MDS_HEALTH_READ_ONLY", cluster="mycluster"}'
values: '1 1 1 1 1 1 1 1 1'
promql_expr_test:
- expr: ceph_health_detail{name="MDS_HEALTH_READ_ONLY"} > 0
eval_time: 2m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="MDS_HEALTH_READ_ONLY", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 1m
alertname: CephFilesystemReadOnly
- eval_time: 5m
alertname: CephFilesystemReadOnly
exp_alerts:
- exp_labels:
name: MDS_HEALTH_READ_ONLY
severity: critical
cluster: mycluster
type: ceph_default
oid: 1.3.6.1.4.1.50495.1.2.1.5.2
exp_annotations:
documentation: https://docs.ceph.com/en/latest/cephfs/health-messages#cephfs-health-messages
summary: CephFS filesystem in read only mode due to write error(s) on cluster mycluster
description: "The filesystem has switched to READ ONLY due to an unexpected error when writing to the metadata pool. Either analyze the output from the MDS daemon admin socket, or escalate to support."
- interval: 1m
input_series:
- series: 'ceph_health_detail{name="MDS_ALL_DOWN", cluster="mycluster"}'
values: '0 0 1 1 1 1 1 1 1 1 1'
promql_expr_test:
- expr: ceph_health_detail{name="MDS_ALL_DOWN"} > 0
eval_time: 2m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="MDS_ALL_DOWN", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 1m
alertname: CephFilesystemOffline
- eval_time: 10m
alertname: CephFilesystemOffline
exp_alerts:
- exp_labels:
name: MDS_ALL_DOWN
severity: critical
cluster: mycluster
type: ceph_default
oid: 1.3.6.1.4.1.50495.1.2.1.5.3
exp_annotations:
documentation: https://docs.ceph.com/en/latest/cephfs/health-messages/#mds-all-down
summary: CephFS filesystem is offline on cluster mycluster
description: "All MDS ranks are unavailable. The MDS daemons managing metadata are down, rendering the filesystem offline."
- interval: 1m
input_series:
- series: 'ceph_health_detail{name="FS_DEGRADED", cluster="mycluster"}'
values: '0 0 1 1 1 1 1 1 1 1 1'
promql_expr_test:
- expr: ceph_health_detail{name="FS_DEGRADED"} > 0
eval_time: 2m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="FS_DEGRADED", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 1m
alertname: CephFilesystemDegraded
- eval_time: 10m
alertname: CephFilesystemDegraded
exp_alerts:
- exp_labels:
name: FS_DEGRADED
severity: critical
cluster: mycluster
type: ceph_default
oid: 1.3.6.1.4.1.50495.1.2.1.5.4
exp_annotations:
documentation: https://docs.ceph.com/en/latest/cephfs/health-messages/#fs-degraded
summary: CephFS filesystem is degraded on cluster mycluster
description: "One or more metadata daemons (MDS ranks) are failed or in a damaged state. At best the filesystem is partially available, at worst the filesystem is completely unusable."
- interval: 1m
input_series:
- series: 'ceph_health_detail{name="MDS_INSUFFICIENT_STANDBY", cluster="mycluster"}'
values: '0 0 1 1 1 1 1 1 1 1 1'
promql_expr_test:
- expr: ceph_health_detail{name="MDS_INSUFFICIENT_STANDBY"} > 0
eval_time: 2m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="MDS_INSUFFICIENT_STANDBY", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 1m
alertname: CephFilesystemInsufficientStandby
- eval_time: 10m
alertname: CephFilesystemInsufficientStandby
exp_alerts:
- exp_labels:
name: MDS_INSUFFICIENT_STANDBY
severity: warning
cluster: mycluster
type: ceph_default
exp_annotations:
documentation: https://docs.ceph.com/en/latest/cephfs/health-messages/#mds-insufficient-standby
summary: Ceph filesystem standby daemons too few on cluster mycluster
description: "The minimum number of standby daemons required by standby_count_wanted is less than the current number of standby daemons. Adjust the standby count or increase the number of MDS daemons."
- interval: 1m
input_series:
- series: 'ceph_health_detail{name="FS_WITH_FAILED_MDS", cluster="mycluster"}'
values: '0 0 1 1 1 1 1 1 1 1 1'
promql_expr_test:
- expr: ceph_health_detail{name="FS_WITH_FAILED_MDS"} > 0
eval_time: 2m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="FS_WITH_FAILED_MDS", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 1m
alertname: CephFilesystemFailureNoStandby
- eval_time: 10m
alertname: CephFilesystemFailureNoStandby
exp_alerts:
- exp_labels:
name: FS_WITH_FAILED_MDS
severity: critical
cluster: mycluster
type: ceph_default
oid: 1.3.6.1.4.1.50495.1.2.1.5.5
exp_annotations:
documentation: https://docs.ceph.com/en/latest/cephfs/health-messages/#fs-with-failed-mds
summary: MDS daemon failed, no further standby available on cluster mycluster
description: "An MDS daemon has failed, leaving only one active rank and no available standby. Investigate the cause of the failure or add a standby MDS."
- interval: 1m
input_series:
- series: 'ceph_health_detail{name="MDS_UP_LESS_THAN_MAX", cluster="mycluster"}'
values: '0 0 1 1 1 1 1 1 1 1 1'
promql_expr_test:
- expr: ceph_health_detail{name="MDS_UP_LESS_THAN_MAX"} > 0
eval_time: 2m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="MDS_UP_LESS_THAN_MAX", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 1m
alertname: CephFilesystemMDSRanksLow
- eval_time: 10m
alertname: CephFilesystemMDSRanksLow
exp_alerts:
- exp_labels:
name: MDS_UP_LESS_THAN_MAX
severity: warning
cluster: mycluster
type: ceph_default
exp_annotations:
documentation: https://docs.ceph.com/en/latest/cephfs/health-messages/#mds-up-less-than-max
summary: Ceph MDS daemon count is lower than configured on cluster mycluster
description: "The filesystem's 'max_mds' setting defines the number of MDS ranks in the filesystem. The current number of active MDS daemons is less than this value."
# MGR
- interval: 1m
input_series:
- series: 'up{job="ceph", instance="ceph-mgr:9283"}'
values: '1+0x2 0+0x10'
promql_expr_test:
- expr: up{job="ceph"} == 0
eval_time: 3m
exp_samples:
- labels: '{__name__="up", job="ceph", instance="ceph-mgr:9283"}'
value: 0
alert_rule_test:
- eval_time: 1m
alertname: CephMgrPrometheusModuleInactive
- eval_time: 10m
alertname: CephMgrPrometheusModuleInactive
exp_alerts:
- exp_labels:
instance: ceph-mgr:9283
job: ceph
severity: critical
type: ceph_default
oid: 1.3.6.1.4.1.50495.1.2.1.6.2
exp_annotations:
summary: The mgr/prometheus module is not available
description: "The mgr/prometheus module at ceph-mgr:9283 is unreachable. This could mean that the module has been disabled or the mgr daemon itself is down. Without the mgr/prometheus module metrics and alerts will no longer function. Open a shell to an admin node or toolbox pod and use 'ceph -s' to to determine whether the mgr is active. If the mgr is not active, restart it, otherwise you can determine module status with 'ceph mgr module ls'. If it is not listed as enabled, enable it with 'ceph mgr module enable prometheus'."
- interval: 1m
input_series:
- series: 'ceph_health_detail{name="RECENT_MGR_MODULE_CRASH", cluster="mycluster"}'
values: '0+0x2 1+0x20'
promql_expr_test:
- expr: ceph_health_detail{name="RECENT_MGR_MODULE_CRASH"} == 1
eval_time: 3m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="RECENT_MGR_MODULE_CRASH", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 1m
alertname: CephMgrModuleCrash
- eval_time: 15m
alertname: CephMgrModuleCrash
exp_alerts:
- exp_labels:
name: RECENT_MGR_MODULE_CRASH
severity: critical
cluster: mycluster
type: ceph_default
oid: 1.3.6.1.4.1.50495.1.2.1.6.1
exp_annotations:
documentation: https://docs.ceph.com/en/latest/rados/operations/health-checks#recent-mgr-module-crash
summary: A manager module has recently crashed on cluster mycluster
description: "One or more mgr modules have crashed and have yet to be acknowledged by an administrator. A crashed module may impact functionality within the cluster. Use the 'ceph crash' command to determine which module has failed, and archive it to acknowledge the failure."
# MON
- interval: 1m
input_series:
- series: 'ceph_health_detail{name="MON_DISK_CRIT", cluster="mycluster"}'
values: '0+0x2 1+0x10'
- series: 'ceph_mon_metadata{ceph_daemon="mon.a", hostname="ceph-mon-a", cluster="mycluster"}'
values: '1+0x13'
promql_expr_test:
- expr: ceph_health_detail{name="MON_DISK_CRIT"} == 1
eval_time: 3m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="MON_DISK_CRIT", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 1m
alertname: CephMonDiskspaceCritical
- eval_time: 10m
alertname: CephMonDiskspaceCritical
exp_alerts:
- exp_labels:
name: "MON_DISK_CRIT"
severity: critical
cluster: mycluster
type: ceph_default
oid: 1.3.6.1.4.1.50495.1.2.1.3.2
exp_annotations:
documentation: https://docs.ceph.com/en/latest/rados/operations/health-checks#mon-disk-crit
summary: Filesystem space on at least one monitor is critically low on cluster mycluster
description: "The free space available to a monitor's store is critically low. You should increase the space available to the monitor(s). The default directory is /var/lib/ceph/mon-*/data/store.db on traditional deployments, and /var/lib/rook/mon-*/data/store.db on the mon pod's worker node for Rook. Look for old, rotated versions of *.log and MANIFEST*. Do NOT touch any *.sst files. Also check any other directories under /var/lib/rook and other directories on the same filesystem, often /var/log and /var/tmp are culprits. Your monitor hosts are; - ceph-mon-a"
- interval: 1m
input_series:
- series: 'ceph_health_detail{name="MON_DISK_LOW", cluster="mycluster"}'
values: '0+0x2 1+0x10'
- series: 'ceph_mon_metadata{ceph_daemon="mon.a", hostname="ceph-mon-a", cluster="mycluster"}'
values: '1+0x13'
promql_expr_test:
- expr: ceph_health_detail{name="MON_DISK_LOW"} == 1
eval_time: 3m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="MON_DISK_LOW", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 1m
alertname: CephMonDiskspaceLow
- eval_time: 10m
alertname: CephMonDiskspaceLow
exp_alerts:
- exp_labels:
name: "MON_DISK_LOW"
severity: warning
cluster: mycluster
type: ceph_default
exp_annotations:
documentation: https://docs.ceph.com/en/latest/rados/operations/health-checks#mon-disk-low
summary: Drive space on at least one monitor is approaching full on cluster mycluster
description: "The space available to a monitor's store is approaching full (>70% is the default). You should increase the space available to the monitor(s). The default directory is /var/lib/ceph/mon-*/data/store.db on traditional deployments, and /var/lib/rook/mon-*/data/store.db on the mon pod's worker node for Rook. Look for old, rotated versions of *.log and MANIFEST*. Do NOT touch any *.sst files. Also check any other directories under /var/lib/rook and other directories on the same filesystem, often /var/log and /var/tmp are culprits. Your monitor hosts are; - ceph-mon-a"
- interval: 1m
input_series:
- series: 'ceph_health_detail{name="MON_CLOCK_SKEW", cluster="mycluster"}'
values: '0+0x2 1+0x10'
promql_expr_test:
- expr: ceph_health_detail{name="MON_CLOCK_SKEW"} == 1
eval_time: 3m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="MON_CLOCK_SKEW", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 1m
alertname: CephMonClockSkew
- eval_time: 10m
alertname: CephMonClockSkew
exp_alerts:
- exp_labels:
name: "MON_CLOCK_SKEW"
severity: warning
cluster: mycluster
type: ceph_default
exp_annotations:
documentation: https://docs.ceph.com/en/latest/rados/operations/health-checks#mon-clock-skew
summary: Clock skew detected among monitors on cluster mycluster
description: "Ceph monitors rely on closely synchronized time to maintain quorum and cluster consistency. This event indicates that the time on at least one mon has drifted too far from the lead mon. Review cluster status with ceph -s. This will show which monitors are affected. Check the time sync status on each monitor host with 'ceph time-sync-status' and the state and peers of your ntpd or chrony daemon."
# Check 3 mons one down, quorum at risk
- interval: 1m
input_series:
- series: 'ceph_health_detail{name="MON_DOWN", cluster="mycluster"}'
values: '0+0x2 1+0x12'
- series: 'ceph_mon_quorum_status{ceph_daemon="mon.a", cluster="mycluster"}'
values: '1+0x14'
- series: 'ceph_mon_quorum_status{ceph_daemon="mon.b", cluster="mycluster"}'
values: '1+0x14'
- series: 'ceph_mon_quorum_status{ceph_daemon="mon.c", cluster="mycluster"}'
values: '1+0x2 0+0x12'
- series: 'ceph_mon_metadata{ceph_daemon="mon.a", hostname="ceph-mon-1", cluster="mycluster"}'
values: '1+0x14'
- series: 'ceph_mon_metadata{ceph_daemon="mon.b", hostname="ceph-mon-2", cluster="mycluster"}'
values: '1+0x14'
- series: 'ceph_mon_metadata{ceph_daemon="mon.c", hostname="ceph-mon-3", cluster="mycluster"}'
values: '1+0x14'
promql_expr_test:
- expr: ((ceph_health_detail{name="MON_DOWN"} == 1) * on() group_right(cluster) (count(ceph_mon_quorum_status == 1) by (cluster) == bool (floor(count(ceph_mon_metadata) by (cluster) / 2) + 1))) == 1
eval_time: 3m
exp_samples:
- labels: '{cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 1m
alertname: CephMonDownQuorumAtRisk
# shouldn't fire
- eval_time: 10m
alertname: CephMonDownQuorumAtRisk
exp_alerts:
- exp_labels:
severity: critical
cluster: mycluster
type: ceph_default
oid: 1.3.6.1.4.1.50495.1.2.1.3.1
exp_annotations:
documentation: https://docs.ceph.com/en/latest/rados/operations/health-checks#mon-down
summary: Monitor quorum is at risk on cluster mycluster
description: "Quorum requires a majority of monitors (x 2) to be active. Without quorum the cluster will become inoperable, affecting all services and connected clients. The following monitors are down: - mon.c on ceph-mon-3"
# check 5 mons, 1 down - warning only
- interval: 1m
input_series:
- series: 'ceph_mon_quorum_status{ceph_daemon="mon.a", cluster="mycluster"}'
values: '1+0x14'
- series: 'ceph_mon_quorum_status{ceph_daemon="mon.b", cluster="mycluster"}'
values: '1+0x14'
- series: 'ceph_mon_quorum_status{ceph_daemon="mon.c", cluster="mycluster"}'
values: '1+0x14'
- series: 'ceph_mon_quorum_status{ceph_daemon="mon.d", cluster="mycluster"}'
values: '1+0x14'
- series: 'ceph_mon_quorum_status{ceph_daemon="mon.e", cluster="mycluster"}'
values: '1+0x2 0+0x12'
- series: 'ceph_mon_metadata{ceph_daemon="mon.a", hostname="ceph-mon-1", cluster="mycluster"}'
values: '1+0x14'
- series: 'ceph_mon_metadata{ceph_daemon="mon.b", hostname="ceph-mon-2", cluster="mycluster"}'
values: '1+0x14'
- series: 'ceph_mon_metadata{ceph_daemon="mon.c", hostname="ceph-mon-3", cluster="mycluster"}'
values: '1+0x14'
- series: 'ceph_mon_metadata{ceph_daemon="mon.d", hostname="ceph-mon-4", cluster="mycluster"}'
values: '1+0x14'
- series: 'ceph_mon_metadata{ceph_daemon="mon.e", hostname="ceph-mon-5", cluster="mycluster"}'
values: '1+0x14'
promql_expr_test:
- expr: (count by (cluster) (ceph_mon_quorum_status == 0)) <= (count by (cluster) (ceph_mon_metadata) - floor((count by (cluster) (ceph_mon_metadata) / 2 + 1)))
eval_time: 3m
exp_samples:
- labels: '{cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 1m
alertname: CephMonDown
- eval_time: 10m
alertname: CephMonDown
exp_alerts:
- exp_labels:
severity: warning
cluster: mycluster
type: ceph_default
exp_annotations:
documentation: https://docs.ceph.com/en/latest/rados/operations/health-checks#mon-down
summary: One or more monitors down on cluster mycluster
description: "You have 1 monitor down. Quorum is still intact, but the loss of an additional monitor will make your cluster inoperable. The following monitors are down: - mon.e on ceph-mon-5"
# Device Health
- interval: 1m
input_series:
- series: 'ceph_health_detail{name="DEVICE_HEALTH", cluster="mycluster"}'
values: '0+0x2 1+0x10'
promql_expr_test:
- expr: ceph_health_detail{name="DEVICE_HEALTH"} == 1
eval_time: 3m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="DEVICE_HEALTH", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 1m
alertname: CephDeviceFailurePredicted
- eval_time: 10m
alertname: CephDeviceFailurePredicted
exp_alerts:
- exp_labels:
name: "DEVICE_HEALTH"
severity: warning
cluster: mycluster
type: ceph_default
exp_annotations:
documentation: https://docs.ceph.com/en/latest/rados/operations/health-checks#id2
summary: Device(s) predicted to fail soon on cluster mycluster
description: "The device health module has determined that one or more devices will fail soon. To review device status use 'ceph device ls'. To show a specific device use 'ceph device info <dev id>'. Mark the OSD out so that data may migrate to other OSDs. Once the OSD has drained, destroy the OSD, replace the device, and redeploy the OSD."
- interval: 1m
input_series:
- series: 'ceph_health_detail{name="DEVICE_HEALTH_TOOMANY", cluster="mycluster"}'
values: '0+0x2 1+0x10'
promql_expr_test:
- expr: ceph_health_detail{name="DEVICE_HEALTH_TOOMANY"} == 1
eval_time: 3m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="DEVICE_HEALTH_TOOMANY", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 1m
alertname: CephDeviceFailurePredictionTooHigh
- eval_time: 10m
alertname: CephDeviceFailurePredictionTooHigh
exp_alerts:
- exp_labels:
name: "DEVICE_HEALTH_TOOMANY"
severity: critical
cluster: mycluster
type: ceph_default
oid: 1.3.6.1.4.1.50495.1.2.1.4.7
exp_annotations:
documentation: https://docs.ceph.com/en/latest/rados/operations/health-checks#device-health-toomany
summary: Too many devices are predicted to fail on cluster mycluster, unable to resolve
description: "The device health module has determined that devices predicted to fail can not be remediated automatically, since too many OSDs would be removed from the cluster to ensure performance and availability. Prevent data integrity issues by adding new OSDs so that data may be relocated."
- interval: 1m
input_series:
- series: 'ceph_health_detail{name="DEVICE_HEALTH_IN_USE", cluster="mycluster"}'
values: '0+0x2 1+0x10'
promql_expr_test:
- expr: ceph_health_detail{name="DEVICE_HEALTH_IN_USE"} == 1
eval_time: 3m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="DEVICE_HEALTH_IN_USE", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 1m
alertname: CephDeviceFailureRelocationIncomplete
- eval_time: 10m
alertname: CephDeviceFailureRelocationIncomplete
exp_alerts:
- exp_labels:
name: "DEVICE_HEALTH_IN_USE"
severity: warning
cluster: mycluster
type: ceph_default
exp_annotations:
documentation: https://docs.ceph.com/en/latest/rados/operations/health-checks#device-health-in-use
summary: Device failure is predicted, but unable to relocate data on cluster mycluster
description: "The device health module has determined that one or more devices will fail soon, but the normal process of relocating the data on the device to other OSDs in the cluster is blocked. \nEnsure that the cluster has available free space. It may be necessary to add capacity to the cluster to allow data from the failing device to successfully migrate, or to enable the balancer."
# OSD
- interval: 1m
input_series:
- series: 'ceph_health_detail{name="OSD_HOST_DOWN", cluster="mycluster"}'
values: '0+0x2 1+0x10'
- series: 'ceph_osd_up{ceph_daemon="osd.0", cluster="mycluster"}'
values: '1+0x2 0+0x10'
- series: 'ceph_osd_metadata{ceph_daemon="osd.0", hostname="ceph-osd-1", cluster="mycluster"}'
values: '1+0x12'
promql_expr_test:
- expr: ceph_health_detail{name="OSD_HOST_DOWN"} == 1
eval_time: 3m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="OSD_HOST_DOWN", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 1m
alertname: CephOSDHostDown
- eval_time: 10m
alertname: CephOSDHostDown
exp_alerts:
- exp_labels:
name: "OSD_HOST_DOWN"
severity: warning
cluster: mycluster
type: ceph_default
oid: 1.3.6.1.4.1.50495.1.2.1.4.8
exp_annotations:
summary: An OSD host is offline on cluster mycluster
description: "The following OSDs are down: - ceph-osd-1 : osd.0"
- interval: 1m
input_series:
- series: 'ceph_health_detail{name="OSD_SLOW_PING_TIME_FRONT", cluster="mycluster"}'
values: '0+0x2 1+0x20'
promql_expr_test:
- expr: ceph_health_detail{name="OSD_SLOW_PING_TIME_FRONT"} == 0
eval_time: 1m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="OSD_SLOW_PING_TIME_FRONT", cluster="mycluster"}'
value: 0
alert_rule_test:
- eval_time: 1m
alertname: CephOSDTimeoutsPublicNetwork
- eval_time: 10m
alertname: CephOSDTimeoutsPublicNetwork
exp_alerts:
- exp_labels:
name: "OSD_SLOW_PING_TIME_FRONT"
severity: warning
cluster: mycluster
type: ceph_default
exp_annotations:
summary: Network issues delaying OSD heartbeats (public network) on cluster mycluster
description: "OSD heartbeats on the cluster's 'public' network (frontend) are running slow. Investigate the network for latency or loss issues. Use 'ceph health detail' to show the affected OSDs."
- interval: 1m
input_series:
- series: 'ceph_health_detail{name="OSD_SLOW_PING_TIME_BACK", cluster="mycluster"}'
values: '0+0x2 1+0x20'
promql_expr_test:
- expr: ceph_health_detail{name="OSD_SLOW_PING_TIME_BACK"} == 0
eval_time: 1m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="OSD_SLOW_PING_TIME_BACK", cluster="mycluster"}'
value: 0
alert_rule_test:
- eval_time: 1m
alertname: CephOSDTimeoutsClusterNetwork
- eval_time: 10m
alertname: CephOSDTimeoutsClusterNetwork
exp_alerts:
- exp_labels:
name: "OSD_SLOW_PING_TIME_BACK"
severity: warning
cluster: mycluster
type: ceph_default
exp_annotations:
summary: Network issues delaying OSD heartbeats (cluster network) on cluster mycluster
description: "OSD heartbeats on the cluster's 'cluster' network (backend) are slow. Investigate the network for latency issues on this subnet. Use 'ceph health detail' to show the affected OSDs."
- interval: 1m
input_series:
- series: 'ceph_health_detail{name="BLUESTORE_DISK_SIZE_MISMATCH", cluster="mycluster"}'
values: '0+0x2 1+0x20'
promql_expr_test:
- expr: ceph_health_detail{name="BLUESTORE_DISK_SIZE_MISMATCH"} == 0
eval_time: 1m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="BLUESTORE_DISK_SIZE_MISMATCH", cluster="mycluster"}'
value: 0
alert_rule_test:
- eval_time: 1m
alertname: CephOSDInternalDiskSizeMismatch
- eval_time: 10m
alertname: CephOSDInternalDiskSizeMismatch
exp_alerts:
- exp_labels:
name: "BLUESTORE_DISK_SIZE_MISMATCH"
severity: warning
cluster: mycluster
type: ceph_default
exp_annotations:
documentation: https://docs.ceph.com/en/latest/rados/operations/health-checks#bluestore-disk-size-mismatch
summary: OSD size inconsistency error on cluster mycluster
description: "One or more OSDs have an internal inconsistency between metadata and the size of the device. This could lead to the OSD(s) crashing in future. You should redeploy the affected OSDs."
- interval: 30s
input_series:
- series: 'ceph_health_detail{name="BLUESTORE_SPURIOUS_READ_ERRORS", cluster="mycluster"}'
values: '0+0x2 1+0x20'
promql_expr_test:
- expr: ceph_health_detail{name="BLUESTORE_SPURIOUS_READ_ERRORS"} == 1
eval_time: 3m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="BLUESTORE_SPURIOUS_READ_ERRORS", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 1m
alertname: CephOSDReadErrors
- eval_time: 10m
alertname: CephOSDReadErrors
exp_alerts:
- exp_labels:
name: "BLUESTORE_SPURIOUS_READ_ERRORS"
severity: warning
cluster: mycluster
type: ceph_default
exp_annotations:
documentation: https://docs.ceph.com/en/latest/rados/operations/health-checks#bluestore-spurious-read-errors
summary: Device read errors detected on cluster mycluster
description: "An OSD has encountered read errors, but the OSD has recovered by retrying the reads. This may indicate an issue with hardware or the kernel."
- interval: 1m
input_series:
- series: 'ceph_health_detail{name="OSD_DOWN", cluster="mycluster"}'
values: '0+0x2 1+0x10'
- series: 'ceph_osd_up{ceph_daemon="osd.0", cluster="mycluster"}'
values: '1+0x12'
- series: 'ceph_osd_up{ceph_daemon="osd.1", cluster="mycluster"}'
values: '1+0x2 0+0x10'
- series: 'ceph_osd_up{ceph_daemon="osd.2", cluster="mycluster"}'
values: '1+0x12'
- series: 'ceph_osd_metadata{ceph_daemon="osd.0", hostname="ceph-osd-1", cluster="mycluster"}'
values: '1+0x12'
- series: 'ceph_osd_metadata{ceph_daemon="osd.1", hostname="ceph-osd-2", cluster="mycluster"}'
values: '1+0x12'
- series: 'ceph_osd_metadata{ceph_daemon="osd.2", hostname="ceph-osd-3", cluster="mycluster"}'
values: '1+0x12'
promql_expr_test:
- expr: ceph_health_detail{name="OSD_DOWN"} == 1
eval_time: 3m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="OSD_DOWN", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 1m
alertname: CephOSDDown
- eval_time: 10m
alertname: CephOSDDown
exp_alerts:
- exp_labels:
name: "OSD_DOWN"
severity: warning
cluster: mycluster
type: ceph_default
oid: 1.3.6.1.4.1.50495.1.2.1.4.2
exp_annotations:
documentation: https://docs.ceph.com/en/latest/rados/operations/health-checks#osd-down
summary: An OSD has been marked down on cluster mycluster
description: "1 OSD down for over 5mins. The following OSD is down: - osd.1 on ceph-osd-2"
- interval: 1m
input_series:
- series: 'ceph_health_detail{name="OSD_NEARFULL", cluster="mycluster"}'
values: '0+0x2 1+0x10'
promql_expr_test:
- expr: ceph_health_detail{name="OSD_NEARFULL"} == 1
eval_time: 3m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="OSD_NEARFULL", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 1m
alertname: CephOSDNearFull
- eval_time: 10m
alertname: CephOSDNearFull
exp_alerts:
- exp_labels:
name: "OSD_NEARFULL"
severity: warning
cluster: mycluster
type: ceph_default
oid: 1.3.6.1.4.1.50495.1.2.1.4.3
exp_annotations:
documentation: https://docs.ceph.com/en/latest/rados/operations/health-checks#osd-nearfull
summary: OSD(s) running low on free space (NEARFULL) on cluster mycluster
description: One or more OSDs have reached the NEARFULL threshold. Use 'ceph health detail' and 'ceph osd df' to identify the problem. To resolve, add capacity to the affected OSD's failure domain, restore down/out OSDs, or delete unwanted data.
- interval: 1m
input_series:
- series: 'ceph_health_detail{name="OSD_FULL", cluster="mycluster"}'
values: '0+0x2 1+0x10'
promql_expr_test:
- expr: ceph_health_detail{name="OSD_FULL"} == 1
eval_time: 3m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="OSD_FULL", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 1m
alertname: CephOSDFull
- eval_time: 10m
alertname: CephOSDFull
exp_alerts:
- exp_labels:
name: "OSD_FULL"
severity: critical
cluster: mycluster
type: ceph_default
oid: 1.3.6.1.4.1.50495.1.2.1.4.6
exp_annotations:
documentation: https://docs.ceph.com/en/latest/rados/operations/health-checks#osd-full
summary: OSD full, writes blocked on cluster mycluster
description: An OSD has reached the FULL threshold. Writes to pools that share the affected OSD will be blocked. Use 'ceph health detail' and 'ceph osd df' to identify the problem. To resolve, add capacity to the affected OSD's failure domain, restore down/out OSDs, or delete unwanted data.
- interval: 1m
input_series:
- series: 'ceph_health_detail{name="OSD_BACKFILLFULL", cluster="mycluster"}'
values: '0+0x2 1+0x10'
promql_expr_test:
- expr: ceph_health_detail{name="OSD_BACKFILLFULL"} == 1
eval_time: 3m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="OSD_BACKFILLFULL", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 1m
alertname: CephOSDBackfillFull
- eval_time: 10m
alertname: CephOSDBackfillFull
exp_alerts:
- exp_labels:
name: "OSD_BACKFILLFULL"
severity: warning
cluster: mycluster
type: ceph_default
exp_annotations:
documentation: https://docs.ceph.com/en/latest/rados/operations/health-checks#osd-backfillfull
summary: OSD(s) too full for backfill operations on cluster mycluster
description: "An OSD has reached the BACKFILL FULL threshold. This will prevent rebalance operations from completing. Use 'ceph health detail' and 'ceph osd df' to identify the problem. To resolve, add capacity to the affected OSD's failure domain, restore down/out OSDs, or delete unwanted data."
- interval: 30s
input_series:
- series: 'ceph_health_detail{name="OSD_TOO_MANY_REPAIRS", cluster="mycluster"}'
values: '0+0x2 1+0x20'
promql_expr_test:
- expr: ceph_health_detail{name="OSD_TOO_MANY_REPAIRS"} == 0
eval_time: 1m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="OSD_TOO_MANY_REPAIRS", cluster="mycluster"}'
value: 0
alert_rule_test:
- eval_time: 1m
alertname: CephOSDTooManyRepairs
- eval_time: 10m
alertname: CephOSDTooManyRepairs
exp_alerts:
- exp_labels:
name: "OSD_TOO_MANY_REPAIRS"
severity: warning
cluster: mycluster
type: ceph_default
exp_annotations:
documentation: https://docs.ceph.com/en/latest/rados/operations/health-checks#osd-too-many-repairs
summary: OSD reports a high number of read errors on cluster mycluster
description: Reads from an OSD have used a secondary PG to return data to the client, indicating a potential failing drive.
# Pools
# trigger percent full prediction on pools 1 and 2 only
- interval: 12h
input_series:
- series: 'ceph_pool_percent_used{pool_id="1", instance="9090", cluster="mycluster"}'
values: '1 1 1 1 1'
- series: 'ceph_pool_percent_used{pool_id="1", instance="8090", cluster="mycluster"}'
values: '78 89 79 98 78'
- series: 'ceph_pool_percent_used{pool_id="2", instance="9090", cluster="mycluster"}'
values: '1 1 1 1 1'
- series: 'ceph_pool_percent_used{pool_id="2", instance="8090", cluster="mycluster"}'
values: '22 22 23 23 24'
- series: 'ceph_pool_metadata{pool_id="1" , instance="9090" ,name="rbd",type="replicated", cluster="mycluster"}'
values: '1 1 1 1 1'
- series: 'ceph_pool_metadata{pool_id="1", instance="8090",name="default.rgw.index",type="replicated", cluster="mycluster"}'
values: '1 1 1 1 1'
- series: 'ceph_pool_metadata{pool_id="2" , instance="9090" ,name="rbd",type="replicated", cluster="mycluster"}'
values: '1 1 1 1 1'
- series: 'ceph_pool_metadata{pool_id="2", instance="8090",name="default.rgw.index",type="replicated", cluster="mycluster"}'
values: '1 1 1 1 1'
promql_expr_test:
- expr: |
(predict_linear(ceph_pool_percent_used[2d], 3600 * 24 * 5) * on(cluster, pool_id, instance)
group_right() ceph_pool_metadata) >= 95
eval_time: 36h
exp_samples:
- labels: '{instance="8090",name="default.rgw.index",pool_id="1",type="replicated", cluster="mycluster"}'
value: 1.435E+02 # 142%
alert_rule_test:
- eval_time: 48h
alertname: CephPoolGrowthWarning
exp_alerts:
- exp_labels:
instance: 8090
name: default.rgw.index
pool_id: 1
severity: warning
cluster: mycluster
type: ceph_default
oid: 1.3.6.1.4.1.50495.1.2.1.9.2
exp_annotations:
summary: Pool growth rate may soon exceed capacity on cluster mycluster
description: Pool 'default.rgw.index' will be full in less than 5 days assuming the average fill-up rate of the past 48 hours.
- interval: 1m
input_series:
- series: 'ceph_health_detail{name="POOL_BACKFILLFULL", cluster="mycluster"}'
values: '0+0x2 1+0x10'
promql_expr_test:
- expr: ceph_health_detail{name="POOL_BACKFILLFULL"} == 1
eval_time: 3m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="POOL_BACKFILLFULL", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 1m
alertname: CephPoolBackfillFull
- eval_time: 5m
alertname: CephPoolBackfillFull
exp_alerts:
- exp_labels:
name: "POOL_BACKFILLFULL"
severity: warning
cluster: mycluster
type: ceph_default
exp_annotations:
summary: Free space in a pool is too low for recovery/backfill on cluster mycluster
description: A pool is approaching the near full threshold, which will prevent recovery/backfill operations from completing. Consider adding more capacity.
- interval: 1m
input_series:
- series: 'ceph_health_detail{name="POOL_NEAR_FULL", cluster="mycluster"}'
values: '0+0x2 1+0x10'
promql_expr_test:
- expr: ceph_health_detail{name="POOL_NEAR_FULL"} == 1
eval_time: 3m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="POOL_NEAR_FULL", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 1m
alertname: CephPoolNearFull
- eval_time: 10m
alertname: CephPoolNearFull
exp_alerts:
- exp_labels:
name: "POOL_NEAR_FULL"
severity: warning
cluster: mycluster
type: ceph_default
exp_annotations:
summary: One or more Ceph pools are nearly full on cluster mycluster
description: "A pool has exceeded the warning (percent full) threshold, or OSDs supporting the pool have reached the NEARFULL threshold. Writes may continue, but you are at risk of the pool going read-only if more capacity isn't made available. Determine the affected pool with 'ceph df detail', looking at QUOTA BYTES and STORED. Increase the pool's quota, or add capacity to the cluster first then increase the pool's quota (e.g. ceph osd pool set quota <pool_name> max_bytes <bytes>). Also ensure that the balancer is active."
# PGs
- interval: 1m
input_series:
- series: 'ceph_health_detail{name="PG_NOT_SCRUBBED",cluster="mycluster"}'
values: '0+0x2 1+0x10'
promql_expr_test:
- expr: ceph_health_detail{name="PG_NOT_SCRUBBED"} == 1
eval_time: 3m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="PG_NOT_SCRUBBED", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 1m
alertname: CephPGNotScrubbed
- eval_time: 10m
alertname: CephPGNotScrubbed
exp_alerts:
- exp_labels:
name: "PG_NOT_SCRUBBED"
severity: warning
cluster: mycluster
type: ceph_default
exp_annotations:
documentation: https://docs.ceph.com/en/latest/rados/operations/health-checks#pg-not-scrubbed
summary: Placement group(s) have not been scrubbed on cluster mycluster
description: "One or more PGs have not been scrubbed recently. Scrubs check metadata integrity, protecting against bit-rot. They check that metadata is consistent across data replicas. When PGs miss their scrub interval, it may indicate that the scrub window is too small, or PGs were not in a 'clean' state during the scrub window. You can manually initiate a scrub with: ceph pg scrub <pgid>"
- interval: 1m
input_series:
- series: 'ceph_health_detail{name="PG_DAMAGED",cluster="mycluster"}'
values: '0+0x4 1+0x20'
promql_expr_test:
- expr: ceph_health_detail{name=~"PG_DAMAGED|OSD_SCRUB_ERRORS"} == 1
eval_time: 5m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="PG_DAMAGED", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 1m
alertname: CephPGsDamaged
- eval_time: 10m
alertname: CephPGsDamaged
exp_alerts:
- exp_labels:
name: "PG_DAMAGED"
severity: critical
cluster: mycluster
type: ceph_default
oid: 1.3.6.1.4.1.50495.1.2.1.7.4
exp_annotations:
documentation: https://docs.ceph.com/en/latest/rados/operations/health-checks#pg-damaged
summary: Placement group damaged, manual intervention needed on cluster mycluster
description: During data consistency checks (scrub), at least one PG has been flagged as being damaged or inconsistent. Check to see which PG is affected, and attempt a manual repair if necessary. To list problematic placement groups, use 'rados list-inconsistent-pg <pool>'. To repair PGs use the 'ceph pg repair <pg_num>' command.
- interval: 1m
input_series:
- series: 'ceph_health_detail{name="TOO_MANY_PGS",cluster="mycluster"}'
values: '0+0x4 1+0x20'
promql_expr_test:
- expr: ceph_health_detail{name="TOO_MANY_PGS"} == 1
eval_time: 5m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="TOO_MANY_PGS", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 1m
alertname: CephPGsHighPerOSD
- eval_time: 10m
alertname: CephPGsHighPerOSD
exp_alerts:
- exp_labels:
name: "TOO_MANY_PGS"
severity: warning
cluster: mycluster
type: ceph_default
exp_annotations:
documentation: https://docs.ceph.com/en/latest/rados/operations/health-checks/#too-many-pgs
summary: Placement groups per OSD is too high on cluster mycluster
description: "The number of placement groups per OSD is too high (exceeds the mon_max_pg_per_osd setting).\n Check that the pg_autoscaler has not been disabled for any pools with 'ceph osd pool autoscale-status', and that the profile selected is appropriate. You may also adjust the target_size_ratio of a pool to guide the autoscaler based on the expected relative size of the pool ('ceph osd pool set cephfs.cephfs.meta target_size_ratio .1') or set the pg_autoscaler mode to 'warn' and adjust pg_num appropriately for one or more pools."
- interval: 1m
input_series:
- series: 'ceph_health_detail{name="PG_RECOVERY_FULL", cluster="mycluster"}'
values: '0+0x2 1+0x20'
promql_expr_test:
- expr: ceph_health_detail{name="PG_RECOVERY_FULL"} == 0
eval_time: 1m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="PG_RECOVERY_FULL", cluster="mycluster"}'
value: 0
alert_rule_test:
- eval_time: 1m
alertname: CephPGRecoveryAtRisk
- eval_time: 10m
alertname: CephPGRecoveryAtRisk
exp_alerts:
- exp_labels:
name: "PG_RECOVERY_FULL"
severity: critical
cluster: mycluster
type: ceph_default
oid: 1.3.6.1.4.1.50495.1.2.1.7.5
exp_annotations:
documentation: https://docs.ceph.com/en/latest/rados/operations/health-checks#pg-recovery-full
summary: OSDs are too full for recovery on cluster mycluster
description: Data redundancy is at risk since one or more OSDs are at or above the 'full' threshold. Add more capacity to the cluster, restore down/out OSDs, or delete unwanted data.
- interval: 1m
input_series:
- series: 'ceph_health_detail{name="PG_BACKFILL_FULL", cluster="mycluster"}'
values: '0+0x2 1+0x20'
promql_expr_test:
- expr: ceph_health_detail{name="PG_BACKFILL_FULL"} == 0
eval_time: 1m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="PG_BACKFILL_FULL", cluster="mycluster"}'
value: 0
alert_rule_test:
- eval_time: 1m
alertname: CephPGBackfillAtRisk
- eval_time: 10m
alertname: CephPGBackfillAtRisk
exp_alerts:
- exp_labels:
name: "PG_BACKFILL_FULL"
severity: critical
cluster: mycluster
type: ceph_default
oid: 1.3.6.1.4.1.50495.1.2.1.7.6
exp_annotations:
documentation: https://docs.ceph.com/en/latest/rados/operations/health-checks#pg-backfill-full
summary: Backfill operations are blocked due to lack of free space on cluster mycluster
description: Data redundancy may be at risk due to lack of free space within the cluster. One or more OSDs have reached the 'backfillfull' threshold. Add more capacity, or delete unwanted data.
- interval: 1m
input_series:
- series: 'ceph_health_detail{name="PG_AVAILABILITY", cluster="mycluster"}'
values: '0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1'
- series: 'ceph_health_detail{name="OSD_DOWN", cluster="mycluster"}'
values: '0 0 0 1 1 1 1 1 1 0 0 0 0 0 0 0'
promql_expr_test:
- expr: ((ceph_health_detail{name="PG_AVAILABILITY"} == 1) - scalar(ceph_health_detail{name="OSD_DOWN"}))
eval_time: 1m
# empty set at 1m
exp_samples:
alert_rule_test:
# PG_AVAILABILITY and OSD_DOWN not firing .. no alert
- eval_time: 1m
alertname: CephPGUnavailableBlockingIO
exp_alerts:
# PG_AVAILABILITY firing, but osd_down is active .. no alert
- eval_time: 5m
alertname: CephPGUnavailableBlockingIO
exp_alerts:
# PG_AVAILABILITY firing, AND OSD_DOWN is not active...raise the alert
- eval_time: 15m
alertname: CephPGUnavailableBlockingIO
exp_alerts:
- exp_labels:
name: "PG_AVAILABILITY"
severity: critical
cluster: mycluster
type: ceph_default
oid: 1.3.6.1.4.1.50495.1.2.1.7.3
exp_annotations:
documentation: https://docs.ceph.com/en/latest/rados/operations/health-checks#pg-availability
summary: PG is unavailable on cluster mycluster, blocking I/O
description: Data availability is reduced, impacting the cluster's ability to service I/O. One or more placement groups (PGs) are in a state that blocks I/O.
- interval: 1m
input_series:
- series: 'ceph_health_detail{name="PG_NOT_DEEP_SCRUBBED", cluster="mycluster"}'
values: '0+0x2 1+0x10'
promql_expr_test:
- expr: ceph_health_detail{name="PG_NOT_DEEP_SCRUBBED"} == 1
eval_time: 3m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="PG_NOT_DEEP_SCRUBBED", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 1m
alertname: CephPGNotDeepScrubbed
- eval_time: 10m
alertname: CephPGNotDeepScrubbed
exp_alerts:
- exp_labels:
name: "PG_NOT_DEEP_SCRUBBED"
severity: warning
cluster: mycluster
type: ceph_default
exp_annotations:
documentation: https://docs.ceph.com/en/latest/rados/operations/health-checks#pg-not-deep-scrubbed
summary: Placement group(s) have not been deep scrubbed on cluster mycluster
description: One or more PGs have not been deep scrubbed recently. Deep scrubs protect against bit-rot. They compare data replicas to ensure consistency. When PGs miss their deep scrub interval, it may indicate that the window is too small or PGs were not in a 'clean' state during the deep-scrub window.
# Prometheus
- interval: 1m
input_series:
- series: 'up{job="myjob"}'
values: '1+0x10'
promql_expr_test:
- expr: absent(up{job="ceph"})
eval_time: 1m
exp_samples:
- labels: '{job="ceph"}'
value: 1
alert_rule_test:
- eval_time: 5m
alertname: PrometheusJobMissing
exp_alerts:
- exp_labels:
job: ceph
severity: critical
type: ceph_default
oid: 1.3.6.1.4.1.50495.1.2.1.12.1
exp_annotations:
summary: The scrape job for Ceph is missing from Prometheus
description: The prometheus job that scrapes from Ceph is no longer defined, this will effectively mean you'll have no metrics or alerts for the cluster. Please review the job definitions in the prometheus.yml file of the prometheus instance.
# RADOS
- interval: 1m
input_series:
- series: 'ceph_health_detail{name="OBJECT_UNFOUND", cluster="mycluster"}'
values: '0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1'
- series: 'ceph_osd_up{ceph_daemon="osd.0", cluster="mycluster"}'
values: '1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1'
- series: 'ceph_osd_up{ceph_daemon="osd.1", cluster="mycluster"}'
values: '1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1'
- series: 'ceph_osd_up{ceph_daemon="osd.2", cluster="mycluster"}'
values: '1 1 1 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1'
- series: 'ceph_osd_metadata{ceph_daemon="osd.0", cluster="mycluster"}'
values: '1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1'
- series: 'ceph_osd_metadata{ceph_daemon="osd.1", cluster="mycluster"}'
values: '1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1'
- series: 'ceph_osd_metadata{ceph_daemon="osd.2", cluster="mycluster"}'
values: '1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1'
promql_expr_test:
- expr: (ceph_health_detail{name="OBJECT_UNFOUND"} == 1) * on() group_right (cluster) (count(ceph_osd_up == 1) by (cluster) == bool count(ceph_osd_metadata) by (cluster)) == 1
eval_time: 1m
exp_samples:
alert_rule_test:
# OBJECT_UNFOUND but osd.2 is down, so don't fire
- eval_time: 5m
alertname: CephObjectMissing
exp_alerts:
# OBJECT_UNFOUND and all osd's are online, so fire
- eval_time: 15m
alertname: CephObjectMissing
exp_alerts:
- exp_labels:
severity: critical
cluster: mycluster
type: ceph_default
oid: 1.3.6.1.4.1.50495.1.2.1.10.1
exp_annotations:
documentation: https://docs.ceph.com/en/latest/rados/operations/health-checks#object-unfound
summary: Object(s) marked UNFOUND on cluster mycluster
description: The latest version of a RADOS object can not be found, even though all OSDs are up. I/O requests for this object from clients will block (hang). Resolving this issue may require the object to be rolled back to a prior version manually, and manually verified.
# Generic Alerts
- interval: 1m
input_series:
- series: 'ceph_health_detail{name="RECENT_CRASH", cluster="mycluster"}'
values: '0 0 0 1 1 1 1 1 1 1 1'
promql_expr_test:
- expr: ceph_health_detail{name="RECENT_CRASH"} == 1
eval_time: 1m
exp_samples:
alert_rule_test:
# not firing
- eval_time: 1m
alertname: CephDaemonCrash
exp_alerts:
# firing
- eval_time: 10m
alertname: CephDaemonCrash
exp_alerts:
- exp_labels:
name: RECENT_CRASH
severity: critical
cluster: mycluster
type: ceph_default
oid: 1.3.6.1.4.1.50495.1.2.1.1.2
exp_annotations:
documentation: https://docs.ceph.com/en/latest/rados/operations/health-checks/#recent-crash
summary: One or more Ceph daemons have crashed, and are pending acknowledgement on cluster mycluster
description: One or more daemons have crashed recently, and need to be acknowledged. This notification ensures that software crashes do not go unseen. To acknowledge a crash, use the 'ceph crash archive <id>' command.
# new rbdmirror alerts tests
# RBD Mirror Alerts
# alert: CephRBDMirrorImagesPerDaemonHigh
- interval: 1m
input_series:
- series: 'ceph_rbd_mirror_snapshot_image_snapshots{ceph_daemon="client.admin.40628", image="image1", namespace="default", pool="data", cluster="mycluster"}'
values: '0+0x20 1+1x130'
- series: 'ceph_rbd_mirror_snapshot_image_snapshots{ceph_daemon="client.admin.40628", image="image2", namespace="default", pool="data", cluster="mycluster"}'
values: '1+1x130 131+0x20'
# prometheus query test
promql_expr_test:
# negative test where there are no samples
- expr: sum by (cluster, ceph_daemon, namespace) (ceph_rbd_mirror_snapshot_image_snapshots) > 100
eval_time: 50m
exp_samples:
# second positive test
- expr: sum by (cluster, ceph_daemon, namespace) (ceph_rbd_mirror_snapshot_image_snapshots) > 100
eval_time: 70m
exp_samples:
- labels: '{ceph_daemon="client.admin.40628", namespace="default", cluster="mycluster"}'
value: 121
# prometheus alert test
alert_rule_test:
# negative test
- eval_time: 30m
alertname: CephRBDMirrorImagesPerDaemonHigh
exp_alerts:
# positive test where alert is fired
- eval_time: 70m
alertname: CephRBDMirrorImagesPerDaemonHigh
exp_alerts:
- exp_labels:
oid: "1.3.6.1.4.1.50495.1.2.1.10.2"
severity: "critical"
cluster: mycluster
type: "ceph_default"
ceph_daemon: "client.admin.40628"
namespace: "default"
exp_annotations:
summary: "Number of image replications are now above 100 on cluster mycluster"
description: "Number of image replications per daemon is not supposed to go beyond threshold 100"
# alert: CephRBDMirrorImagesNotInSync
- interval: 1m
input_series:
- series: 'ceph_rbd_mirror_snapshot_image_local_timestamp{ceph_daemon="client.admin.40628",image="image1",namespace="default",pool="data",cluster="mycluster"}'
values: '1.678+0x20 2.03+0x20 3.21+0x20'
- series: 'ceph_rbd_mirror_snapshot_image_remote_timestamp{ceph_daemon="client.admin.40628",image="image1",namespace="default",pool="data",cluster="mycluster"}'
values: '1.678+0x20 2.03+0x20 2.03+0x20'
# prometheus query test
promql_expr_test:
# negative test where there are no samples
- expr: sum by (cluster, ceph_daemon, image, namespace, pool) (topk by (cluster, ceph_daemon, image, namespace, pool) (1, ceph_rbd_mirror_snapshot_image_local_timestamp) - topk by (cluster, ceph_daemon, image, namespace, pool) (1, ceph_rbd_mirror_snapshot_image_remote_timestamp)) != 0
eval_time: 30m
exp_samples:
# second positive test
- expr: sum by (cluster, ceph_daemon, image, namespace, pool) (topk by (cluster, ceph_daemon, image, namespace, pool) (1, ceph_rbd_mirror_snapshot_image_local_timestamp) - topk by (cluster, ceph_daemon, image, namespace, pool) (1, ceph_rbd_mirror_snapshot_image_remote_timestamp)) != 0
eval_time: 45m
exp_samples:
- labels: '{ceph_daemon="client.admin.40628", image="image1", namespace="default", pool="data", cluster="mycluster"}'
value: 1.1800000000000002
# prometheus alert test
alert_rule_test:
# negative test
- eval_time: 20m
alertname: CephRBDMirrorImagesNotInSync
exp_alerts:
# positive test where alert is fired
- eval_time: 50m
alertname: CephRBDMirrorImagesNotInSync
exp_alerts:
- exp_labels:
image: "image1"
pool: "data"
oid: "1.3.6.1.4.1.50495.1.2.1.10.3"
severity: "critical"
cluster: mycluster
type: "ceph_default"
ceph_daemon: "client.admin.40628"
namespace: "default"
exp_annotations:
summary: "Some of the RBD mirror images are not in sync with the remote counter parts on cluster mycluster"
description: "Both local and remote RBD mirror images should be in sync."
# alert: CephRBDMirrorImagesNotInSyncVeryHigh
- interval: 1m
input_series:
- series: 'ceph_rbd_mirror_snapshot_image_local_timestamp{ceph_daemon="client.admin.40628",image="image1",namespace="default",pool="data",cluster="mycluster"}'
values: '1.678+0x20 2.03+0x20 3.21+0x20'
- series: 'ceph_rbd_mirror_snapshot_image_remote_timestamp{ceph_daemon="client.admin.40628",image="image1",namespace="default",pool="data",cluster="mycluster"}'
values: '1.678+0x20 2.03+0x20 2.03+0x20'
- series: 'ceph_rbd_mirror_snapshot_image_local_timestamp{ceph_daemon="client.admin.40628",image="image2",namespace="default",pool="data",cluster="mycluster"}'
values: '2.189+0x20 3.301+0x14 3.301+0x26'
- series: 'ceph_rbd_mirror_snapshot_image_remote_timestamp{ceph_daemon="client.admin.40628",image="image2",namespace="default",pool="data",cluster="mycluster"}'
values: '2.189+0x20 3.301+0x14 7.13+0x26'
- series: 'ceph_rbd_mirror_snapshot_image_local_timestamp{ceph_daemon="client.admin.40628",image="image3",namespace="default",pool="data",cluster="mycluster"}'
values: '2.189+0x20 3.301+0x14 3.301+0x26'
- series: 'ceph_rbd_mirror_snapshot_image_remote_timestamp{ceph_daemon="client.admin.40628",image="image3",namespace="default",pool="data",cluster="mycluster"}'
values: '2.189+0x20 3.301+0x14 7.13+0x26'
- series: 'ceph_rbd_mirror_snapshot_image_local_timestamp{ceph_daemon="client.admin.40628",image="image4",namespace="default",pool="data",cluster="mycluster"}'
values: '2.189+0x65'
- series: 'ceph_rbd_mirror_snapshot_image_remote_timestamp{ceph_daemon="client.admin.40628",image="image4",namespace="default",pool="data",cluster="mycluster"}'
values: '2.189+0x65'
- series: 'ceph_rbd_mirror_snapshot_snapshots{ceph_daemon="client.admin.40628",cluster="mycluster"}'
values: '1+0x20 2+0x45'
# prometheus query test
promql_expr_test:
# test each query individually
# query 1
- expr: count by (ceph_daemon, cluster) ((topk by (ceph_daemon, image, namespace, pool) (1, ceph_rbd_mirror_snapshot_image_local_timestamp) - topk by (ceph_daemon, image, namespace, pool) (1, ceph_rbd_mirror_snapshot_image_remote_timestamp)) != 0)
eval_time: 45m
exp_samples:
- labels: '{ceph_daemon="client.admin.40628",cluster="mycluster"}'
value: 3
# query 2
- expr: sum by (ceph_daemon, cluster) (ceph_rbd_mirror_snapshot_snapshots) * .1
eval_time: 45m
exp_samples:
- labels: '{ceph_daemon="client.admin.40628",cluster="mycluster"}'
value: 0.2
# prometheus alert test
alert_rule_test:
# negative test
- eval_time: 2m
alertname: CephRBDMirrorImagesNotInSyncVeryHigh
exp_alerts:
# positive test where alert is fired
- eval_time: 50m
alertname: CephRBDMirrorImagesNotInSyncVeryHigh
exp_alerts:
- exp_labels:
ceph_daemon: "client.admin.40628"
oid: "1.3.6.1.4.1.50495.1.2.1.10.4"
severity: "critical"
cluster: mycluster
type: "ceph_default"
exp_annotations:
summary: "Number of unsynchronized images are very high on cluster mycluster"
description: "More than 10% of the images have synchronization problems."
# alert: "CephRBDMirrorImageTransferBandwidthHigh"
- interval: 1m
input_series:
- series: 'ceph_rbd_mirror_journal_replay_bytes{ceph_daemon="client.admin.40628", cluster="mycluster"}'
values: '0+0x10 1+0x5 10+30x25 736+200x30'
# prometheus query test
promql_expr_test:
# test each couple of rates
# rate 1
- expr: rate(ceph_rbd_mirror_journal_replay_bytes[5m])
eval_time: 5m
exp_samples:
- labels: '{ceph_daemon="client.admin.40628", cluster="mycluster"}'
value: 0.0
# rate 2
- expr: rate(ceph_rbd_mirror_journal_replay_bytes[5m])
eval_time: 20m
exp_samples:
- labels: '{ceph_daemon="client.admin.40628", cluster="mycluster"}'
value: 0.33
# rate 3
- expr: rate(ceph_rbd_mirror_journal_replay_bytes[5m])
eval_time: 40m
exp_samples:
- labels: '{ceph_daemon="client.admin.40628", cluster="mycluster"}'
value: 0.5
# rate 4
- expr: rate(ceph_rbd_mirror_journal_replay_bytes[5m])
eval_time: 50m
exp_samples:
- labels: '{ceph_daemon="client.admin.40628", cluster="mycluster"}'
value: 3.3333333333333335
# prometheus alert test
alert_rule_test:
# negative test
- eval_time: 2m
alertname: CephRBDMirrorImageTransferBandwidthHigh
exp_alerts:
# positive test where alert is fired
- eval_time: 50m
alertname: CephRBDMirrorImageTransferBandwidthHigh
exp_alerts:
- exp_labels:
ceph_daemon: "client.admin.40628"
oid: "1.3.6.1.4.1.50495.1.2.1.10.5"
severity: "warning"
cluster: mycluster
type: "ceph_default"
exp_annotations:
summary: "The replication network usage on cluster mycluster has been increased over 80% in the last 30 minutes. Review the number of images being replicated. This alert will be cleaned automatically after 30 minutes"
description: "Detected a heavy increase in bandwidth for rbd replications (over 80%) in the last 30 min. This might not be a problem, but it is good to review the number of images being replicated simultaneously"
- interval: 30s
input_series:
- series: 'ceph_health_detail{name="HARDWARE_STORAGE", cluster="mycluster"}'
values: '1+0x40'
promql_expr_test:
- expr: ceph_health_detail{name="HARDWARE_STORAGE"} > 0
eval_time: 2m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="HARDWARE_STORAGE", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 1m
alertname: HardwareStorageError
- eval_time: 5m
alertname: HardwareStorageError
exp_alerts:
- exp_labels:
name: HARDWARE_STORAGE
severity: critical
cluster: mycluster
type: ceph_default
oid: 1.3.6.1.4.1.50495.1.2.1.13.1
exp_annotations:
summary: Storage devices error(s) detected on cluster mycluster
description: "Some storage devices are in error. Check `ceph health detail`."
- interval: 30s
input_series:
- series: 'ceph_health_detail{name="HARDWARE_MEMORY", cluster="mycluster"}'
values: '1+0x40'
promql_expr_test:
- expr: ceph_health_detail{name="HARDWARE_MEMORY"} > 0
eval_time: 2m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="HARDWARE_MEMORY", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 1m
alertname: HardwareMemoryError
- eval_time: 5m
alertname: HardwareMemoryError
exp_alerts:
- exp_labels:
name: HARDWARE_MEMORY
severity: critical
cluster: mycluster
type: ceph_default
oid: 1.3.6.1.4.1.50495.1.2.1.13.2
exp_annotations:
summary: DIMM error(s) detected on cluster mycluster
description: "DIMM error(s) detected. Check `ceph health detail`."
- interval: 30s
input_series:
- series: 'ceph_health_detail{name="HARDWARE_PROCESSOR", cluster="mycluster"}'
values: '1+0x40'
promql_expr_test:
- expr: ceph_health_detail{name="HARDWARE_PROCESSOR"} > 0
eval_time: 2m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="HARDWARE_PROCESSOR", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 1m
alertname: HardwareProcessorError
- eval_time: 5m
alertname: HardwareProcessorError
exp_alerts:
- exp_labels:
name: HARDWARE_PROCESSOR
severity: critical
cluster: mycluster
type: ceph_default
oid: 1.3.6.1.4.1.50495.1.2.1.13.3
exp_annotations:
summary: Processor error(s) detected on cluster mycluster
description: "Processor error(s) detected. Check `ceph health detail`."
- interval: 30s
input_series:
- series: 'ceph_health_detail{name="HARDWARE_NETWORK", cluster="mycluster"}'
values: '1+0x40'
promql_expr_test:
- expr: ceph_health_detail{name="HARDWARE_NETWORK"} > 0
eval_time: 2m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="HARDWARE_NETWORK", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 1m
alertname: HardwareNetworkError
- eval_time: 5m
alertname: HardwareNetworkError
exp_alerts:
- exp_labels:
name: HARDWARE_NETWORK
severity: critical
cluster: mycluster
type: ceph_default
oid: 1.3.6.1.4.1.50495.1.2.1.13.4
exp_annotations:
summary: Network error(s) detected on cluster mycluster
description: "Network error(s) detected. Check `ceph health detail`."
- interval: 30s
input_series:
- series: 'ceph_health_detail{name="HARDWARE_POWER", cluster="mycluster"}'
values: '1+0x40'
promql_expr_test:
- expr: ceph_health_detail{name="HARDWARE_POWER"} > 0
eval_time: 2m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="HARDWARE_POWER", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 1m
alertname: HardwarePowerError
- eval_time: 5m
alertname: HardwarePowerError
exp_alerts:
- exp_labels:
name: HARDWARE_POWER
severity: critical
cluster: mycluster
type: ceph_default
oid: 1.3.6.1.4.1.50495.1.2.1.13.5
exp_annotations:
summary: Power supply error(s) detected on cluster mycluster
description: "Power supply error(s) detected. Check `ceph health detail`."
- interval: 30s
input_series:
- series: 'ceph_health_detail{name="HARDWARE_FANS", cluster="mycluster"}'
values: '1+0x40'
promql_expr_test:
- expr: ceph_health_detail{name="HARDWARE_FANS"} > 0
eval_time: 2m
exp_samples:
- labels: '{__name__="ceph_health_detail", name="HARDWARE_FANS", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 1m
alertname: HardwareFanError
- eval_time: 5m
alertname: HardwareFanError
exp_alerts:
- exp_labels:
name: HARDWARE_FANS
severity: critical
cluster: mycluster
type: ceph_default
oid: 1.3.6.1.4.1.50495.1.2.1.13.6
exp_annotations:
summary: Fan error(s) detected on cluster mycluster
description: "Fan error(s) detected. Check `ceph health detail`."
# nvmeof Tests
# NVMeoFSubsystemNamespaceLimit
- interval: 1m
input_series:
- series: 'ceph_nvmeof_subsystem_namespace_limit{nqn="wah", cluster="mycluster"}'
values: '5x10'
- series: 'ceph_nvmeof_subsystem_namespace_metadata{nqn="wah", bdev_name="disk1", cluster="mycluster"}'
values: '1x10'
- series: 'ceph_nvmeof_subsystem_namespace_metadata{nqn="wah", bdev_name="disk2", cluster="mycluster"}'
values: '1x10'
- series: 'ceph_nvmeof_subsystem_namespace_metadata{nqn="wah", bdev_name="disk3", cluster="mycluster"}'
values: '1x10'
- series: 'ceph_nvmeof_subsystem_namespace_metadata{nqn="wah", bdev_name="disk4", cluster="mycluster"}'
values: '1x10'
- series: 'ceph_nvmeof_subsystem_namespace_metadata{nqn="wah", bdev_name="disk5", cluster="mycluster"}'
values: '1x10'
- series: 'ceph_nvmeof_subsystem_namespace_metadata{nqn="wah", bdev_name="disk6", cluster="mycluster"}'
values: '1x10'
promql_expr_test:
- expr: (count by(nqn, cluster) (ceph_nvmeof_subsystem_namespace_metadata)) >= ceph_nvmeof_subsystem_namespace_limit
eval_time: 1m
exp_samples:
- labels: '{nqn="wah",cluster="mycluster"}'
value: 6
alert_rule_test:
- eval_time: 5m
alertname: NVMeoFSubsystemNamespaceLimit
exp_alerts:
- exp_labels:
nqn: wah
severity: warning
cluster: mycluster
type: ceph_default
exp_annotations:
summary: "wah subsystem has reached its maximum number of namespaces on cluster mycluster"
description: "Subsystems have a max namespace limit defined at creation time. This alert means that no more namespaces can be added to wah"
# NVMeoFTooManyGateways
- interval: 1m
input_series:
- series: 'ceph_nvmeof_gateway_info{addr="1.1.1.1",cluster="mycluster"}'
values: '1+0x20'
- series: 'ceph_nvmeof_gateway_info{addr="1.1.1.2",cluster="mycluster"}'
values: '1+0x20'
- series: 'ceph_nvmeof_gateway_info{addr="1.1.1.3",cluster="mycluster"}'
values: '1+0x20'
- series: 'ceph_nvmeof_gateway_info{addr="1.1.1.4",cluster="mycluster"}'
values: '1+0x20'
- series: 'ceph_nvmeof_gateway_info{addr="1.1.1.5",cluster="mycluster"}'
values: '1+0x20'
promql_expr_test:
- expr: count(ceph_nvmeof_gateway_info) by (cluster) > 4.00
eval_time: 1m
exp_samples:
- labels: '{cluster="mycluster"}'
value: 5
alert_rule_test:
- eval_time: 5m
alertname: NVMeoFTooManyGateways
exp_alerts:
- exp_labels:
severity: warning
cluster: mycluster
type: ceph_default
exp_annotations:
summary: "Max supported gateways exceeded on cluster mycluster"
description: "You may create many gateways, but 4 is the tested limit"
# NVMeoFMaxGatewayGroupSize
- interval: 1m
input_series:
- series: 'ceph_nvmeof_gateway_info{group="group-1",addr="1.1.1.1",cluster="mycluster"}'
values: '1+0x20'
- series: 'ceph_nvmeof_gateway_info{group="group-1",addr="1.1.1.2",cluster="mycluster"}'
values: '1+0x20'
- series: 'ceph_nvmeof_gateway_info{group="group-1",addr="1.1.1.3",cluster="mycluster"}'
values: '1+0x20'
- series: 'ceph_nvmeof_gateway_info{group="group-1",addr="1.1.1.9",cluster="mycluster"}'
values: '1+0x20'
- series: 'ceph_nvmeof_gateway_info{group="group-1",addr="1.1.1.12",cluster="mycluster"}'
values: '1+0x20'
- series: 'ceph_nvmeof_gateway_info{group="group-2",addr="1.1.1.4",cluster="mycluster"}'
values: '1+0x20'
- series: 'ceph_nvmeof_gateway_info{group="group-2",addr="1.1.1.5",cluster="mycluster"}'
values: '1+0x20'
promql_expr_test:
- expr: count(ceph_nvmeof_gateway_info) by (cluster, group) > 4.00
eval_time: 1m
exp_samples:
- labels: '{cluster="mycluster",group="group-1"}'
value: 5
alert_rule_test:
- eval_time: 5m
alertname: NVMeoFMaxGatewayGroupSize
exp_alerts:
- exp_labels:
group: group-1
severity: warning
cluster: mycluster
type: ceph_default
exp_annotations:
summary: "Max gateways within a gateway group (group-1) exceeded on cluster mycluster"
description: "You may create many gateways in a gateway group, but 4 is the tested limit"
# NVMeoFSingleGatewayGroup
- interval: 1m
input_series:
- series: 'ceph_nvmeof_gateway_info{group="group-1",addr="1.1.1.2",cluster="mycluster"}'
values: '1+0x20'
- series: 'ceph_nvmeof_gateway_info{group="group-2",addr="1.1.1.4",cluster="mycluster"}'
values: '1+0x20'
- series: 'ceph_nvmeof_gateway_info{group="group-2",addr="1.1.1.5",cluster="mycluster"}'
values: '1+0x20'
promql_expr_test:
- expr: count by(group, cluster) (ceph_nvmeof_gateway_info) == 1
eval_time: 1m
exp_samples:
- labels: '{group="group-1", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 5m
alertname: NVMeoFSingleGatewayGroup
exp_alerts:
- exp_labels:
group: group-1
severity: warning
cluster: mycluster
type: ceph_default
exp_annotations:
summary: "The gateway group group-1 consists of a single gateway - HA is not possible on cluster mycluster"
description: "Although a single member gateway group is valid, it should only be used for test purposes"
# NVMeoFHighGatewayCPU
- interval: 1m
input_series:
- series: 'ceph_nvmeof_reactor_seconds_total{mode="busy",name="nvmf_tgt_poll_group_0",instance="node-1:10008",cluster="mycluster"}'
values: '880+5080x20'
promql_expr_test:
- expr: label_replace(avg by(instance, cluster) (rate(ceph_nvmeof_reactor_seconds_total{mode="busy"}[1m])),"instance","$1","instance","(.*):.*") > 80
eval_time: 5m
exp_samples:
- labels: '{instance="node-1", cluster="mycluster"}'
value: 8.466666666666667E+01
alert_rule_test:
- eval_time: 15m
alertname: NVMeoFHighGatewayCPU
exp_alerts:
- exp_labels:
instance: node-1
severity: warning
cluster: mycluster
type: ceph_default
exp_annotations:
summary: "CPU used by node-1 NVMe-oF Gateway is high on cluster mycluster"
description: "Typically, high CPU may indicate degraded performance. Consider increasing the number of reactor cores"
# NVMeoFGatewayOpenSecurity
- interval: 1m
input_series:
- series: 'ceph_nvmeof_subsystem_metadata{nqn="nqn.good", allow_any_host="no", cluster="mycluster"}'
values: '1+0x10'
- series: 'ceph_nvmeof_subsystem_metadata{nqn="nqn.bad", allow_any_host="yes", cluster="mycluster"}'
values: '1+0x10'
promql_expr_test:
- expr: ceph_nvmeof_subsystem_metadata{allow_any_host="yes"}
eval_time: 1m
exp_samples:
- labels: '{__name__="ceph_nvmeof_subsystem_metadata",nqn="nqn.bad",allow_any_host="yes", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 5m
alertname: NVMeoFGatewayOpenSecurity
exp_alerts:
- exp_labels:
allow_any_host: yes
nqn: nqn.bad
severity: warning
cluster: mycluster
type: ceph_default
exp_annotations:
summary: "Subsystem nqn.bad has been defined without host level security on cluster mycluster"
description: "It is good practice to ensure subsystems use host security to reduce the risk of unexpected data loss"
# NVMeoFTooManySubsystems
- interval: 1m
input_series:
- series: 'ceph_nvmeof_subsystem_metadata{instance="node-1:10008",nqn="nqn1",cluster="mycluster"}'
values: '1+0x10'
- series: 'ceph_nvmeof_subsystem_metadata{instance="node-1:10008",nqn="nqn2",cluster="mycluster"}'
values: '1+0x10'
- series: 'ceph_nvmeof_subsystem_metadata{instance="node-1:10008",nqn="nqn3",cluster="mycluster"}'
values: '1+0x10'
- series: 'ceph_nvmeof_subsystem_metadata{instance="node-1:10008",nqn="nqn4",cluster="mycluster"}'
values: '1+0x10'
- series: 'ceph_nvmeof_subsystem_metadata{instance="node-1:10008",nqn="nqn5",cluster="mycluster"}'
values: '1+0x10'
- series: 'ceph_nvmeof_subsystem_metadata{instance="node-1:10008",nqn="nqn6",cluster="mycluster"}'
values: '1+0x10'
- series: 'ceph_nvmeof_subsystem_metadata{instance="node-1:10008",nqn="nqn7",cluster="mycluster"}'
values: '1+0x10'
- series: 'ceph_nvmeof_subsystem_metadata{instance="node-1:10008",nqn="nqn8",cluster="mycluster"}'
values: '1+0x10'
- series: 'ceph_nvmeof_subsystem_metadata{instance="node-1:10008",nqn="nqn9",cluster="mycluster"}'
values: '1+0x10'
- series: 'ceph_nvmeof_subsystem_metadata{instance="node-1:10008",nqn="nqn10",cluster="mycluster"}'
values: '1+0x10'
- series: 'ceph_nvmeof_subsystem_metadata{instance="node-1:10008",nqn="nqn11",cluster="mycluster"}'
values: '1+0x10'
- series: 'ceph_nvmeof_subsystem_metadata{instance="node-1:10008",nqn="nqn12",cluster="mycluster"}'
values: '1+0x10'
- series: 'ceph_nvmeof_subsystem_metadata{instance="node-1:10008",nqn="nqn13",cluster="mycluster"}'
values: '1+0x10'
- series: 'ceph_nvmeof_subsystem_metadata{instance="node-1:10008",nqn="nqn14",cluster="mycluster"}'
values: '1+0x10'
- series: 'ceph_nvmeof_subsystem_metadata{instance="node-1:10008",nqn="nqn15",cluster="mycluster"}'
values: '1+0x10'
- series: 'ceph_nvmeof_subsystem_metadata{instance="node-1:10008",nqn="nqn16",cluster="mycluster"}'
values: '1+0x10'
- series: 'ceph_nvmeof_subsystem_metadata{instance="node-1:10008",nqn="nqn17",cluster="mycluster"}'
values: '1+0x10'
promql_expr_test:
- expr: count by(gateway_host, cluster) (label_replace(ceph_nvmeof_subsystem_metadata,"gateway_host","$1","instance","(.*):.*")) > 16
eval_time: 1m
exp_samples:
- labels: '{gateway_host="node-1", cluster="mycluster"}'
value: 17
alert_rule_test:
- eval_time: 5m
alertname: NVMeoFTooManySubsystems
exp_alerts:
- exp_labels:
gateway_host: node-1
severity: warning
cluster: mycluster
type: ceph_default
exp_annotations:
summary: "The number of subsystems defined to the gateway exceeds supported values on cluster mycluster"
description: "Although you may continue to create subsystems in node-1, the configuration may not be supported"
# NVMeoFVersionMismatch
- interval: 1m
input_series:
- series: 'ceph_nvmeof_gateway_info{version="0.0.7",cluster="mycluster"}'
values: '1+0x80'
- series: 'ceph_nvmeof_gateway_info{version="1.0.0",cluster="mycluster"}'
values: '1+0x80'
promql_expr_test:
- expr: count(count(ceph_nvmeof_gateway_info) by (cluster, version)) by (cluster) > 1
eval_time: 1m
exp_samples:
- labels: '{cluster="mycluster"}'
value: 2
alert_rule_test:
- eval_time: 1h
alertname: NVMeoFVersionMismatch
exp_alerts:
- exp_labels:
severity: warning
cluster: mycluster
type: ceph_default
exp_annotations:
summary: "Too many different NVMe-oF gateway releases active on cluster mycluster"
description: "This may indicate an issue with deployment. Check cephadm logs"
# NVMeoFHighClientCount
- interval: 1m
input_series:
- series: 'ceph_nvmeof_subsystem_host_count{nqn="nqn1",cluster="mycluster"}'
values: '2 2 2 4 4 8 8 8 10 10 20 20 32 34 34 38 38 40 44 44'
- series: 'ceph_nvmeof_subsystem_host_count{nqn="nqn2",cluster="mycluster"}'
values: '2 2 2 8 8 8 16 16 16 16 16 16 16 16 16 16 16 16 16 16'
promql_expr_test:
- expr: ceph_nvmeof_subsystem_host_count > 32.00
eval_time: 15m
exp_samples:
- labels: '{__name__="ceph_nvmeof_subsystem_host_count",nqn="nqn1",cluster="mycluster"}'
value: 38
alert_rule_test:
- eval_time: 20m
alertname: NVMeoFHighClientCount
exp_alerts:
- exp_labels:
nqn: nqn1
severity: warning
cluster: mycluster
type: ceph_default
exp_annotations:
summary: "The number of clients connected to nqn1 is too high on cluster mycluster"
description: "The supported limit for clients connecting to a subsystem is 32"
# NVMeoFMissingListener
- interval: 1m
input_series:
- series: 'ceph_nvmeof_subsystem_listener_count{nqn="nqn1", instance="node-1:9100"}'
values: '0 0 0 0 0 0 0 0 0 0 0'
- series: 'ceph_nvmeof_subsystem_listener_count{nqn="nqn1", instance="node-2:9100"}'
values: '1 1 1 1 1 1 1 1 1 1 1'
- series: 'ceph_nvmeof_subsystem_listener_count{nqn="nqn1", instance="node-3:9100"}'
values: '1 1 1 1 1 1 1 1 1 1 1'
- series: 'ceph_nvmeof_gateway_info{addr="1.1.1.1", instance="node-1:9100"}'
values: '1+0x20'
- series: 'ceph_nvmeof_gateway_info{addr="1.1.1.2", instance="node-2:9100"}'
values: '1+0x20'
- series: 'ceph_nvmeof_gateway_info{addr="1.1.1.3", instance="node-3:9100"}'
values: '1+0x20'
- series: 'ceph_nvmeof_gateway_info{addr="1.1.1.4", instance="node-4:9100"}'
values: '1+0x20'
promql_expr_test:
- expr: ceph_nvmeof_subsystem_listener_count == 0 and on(nqn) sum(ceph_nvmeof_subsystem_listener_count) by (nqn) > 0
eval_time: 1m
exp_samples:
- labels: '{__name__="ceph_nvmeof_subsystem_listener_count", instance="node-1:9100", nqn="nqn1"}'
value: 0
alert_rule_test:
- eval_time: 10m
alertname: NVMeoFMissingListener
exp_alerts:
- exp_labels:
instance: node-1:9100
nqn: nqn1
severity: warning
type: ceph_default
exp_annotations:
summary: "No listener added for node-1:9100 NVMe-oF Gateway to nqn1 subsystem"
description: "For every subsystem, each gateway should have a listener to balance traffic between gateways."
# NVMeoFZeroListenerSubsystem
- interval: 1m
input_series:
- series: 'ceph_nvmeof_subsystem_listener_count{nqn="nqn1"}'
values: '0 0 0 0 0 0 0 0'
- series: 'ceph_nvmeof_subsystem_listener_count{nqn="nqn2"}'
values: '0 1 1 1 2 2 3 4'
- series: 'ceph_nvmeof_gateway_info{addr="1.1.1.1"}'
values: '1+0x20'
- series: 'ceph_nvmeof_gateway_info{addr="1.1.1.2"}'
values: '1+0x20'
- series: 'ceph_nvmeof_gateway_info{addr="1.1.1.3"}'
values: '1+0x20'
- series: 'ceph_nvmeof_gateway_info{addr="1.1.1.4"}'
values: '1+0x20'
promql_expr_test:
- expr: ceph_nvmeof_subsystem_listener_count == 0
eval_time: 1m
exp_samples:
- labels: '{__name__="ceph_nvmeof_subsystem_listener_count",nqn="nqn1"}'
value: 0
alert_rule_test:
- eval_time: 10m
alertname: NVMeoFZeroListenerSubsystem
exp_alerts:
- exp_labels:
nqn: nqn1
severity: warning
type: ceph_default
exp_annotations:
summary: "No listeners added to nqn1 subsystem"
description: "NVMeoF gateway configuration incomplete; one of the subsystems have zero listeners."
# NVMeoFHighHostCPU
- interval: 1m
input_series:
- series: 'node_cpu_seconds_total{mode="idle",instance="node-1:9100",cpu="0",cluster="mycluster"}'
values: '0+18x10 180+9x20'
- series: 'node_cpu_seconds_total{mode="idle",instance="node-1:9100",cpu="1",cluster="mycluster"}'
values: '0+18x10 180+9x20'
- series: 'ceph_nvmeof_gateway_info{instance="node-1:10008",cluster="mycluster"}'
values: '1.00+0x20'
promql_expr_test:
- expr: 100-((100*(avg by(host) (label_replace(rate(node_cpu_seconds_total{mode="idle"}[5m]),"host","$1","instance","(.*):.*")) * on(host) group_right label_replace(ceph_nvmeof_gateway_info,"host","$1","instance","(.*):.*")))) >= 80
eval_time: 16m
exp_samples:
- labels: '{host="node-1",instance="node-1:10008",cluster="mycluster"}'
value: 85
alert_rule_test:
# negative match at 15m
- eval_time: 15m
alertname: NVMeoFHighHostCPU
# positive match at 25m
- eval_time: 25m
alertname: NVMeoFHighHostCPU
exp_alerts:
- exp_labels:
instance: node-1:10008
host: node-1
cluster: mycluster
severity: warning
type: ceph_default
exp_annotations:
summary: "The CPU is high (85%) on NVMeoF Gateway host (node-1) on cluster mycluster"
description: "High CPU on a gateway host can lead to CPU contention and performance degradation"
# NVMeoFInterfaceDown - triggered on eth0 only
- interval: 30s
input_series:
- series: 'ceph_nvmeof_subsystem_listener_iface_info{operstate="down", device="eth0", cluster="mycluster"}'
values: '1+0x30'
- series: 'ceph_nvmeof_subsystem_listener_iface_info{operstate="up", device="eth1", cluster="mycluster"}'
values: '1+0x30'
promql_expr_test:
- expr: ceph_nvmeof_subsystem_listener_iface_info{operstate="down"}
eval_time: 1m
exp_samples:
- labels: '{__name__="ceph_nvmeof_subsystem_listener_iface_info", device="eth0", operstate="down", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 5m
alertname: NVMeoFInterfaceDown
exp_alerts:
- exp_labels:
oid: 1.3.6.1.4.1.50495.1.2.1.14.1
operstate: down
device: eth0
cluster: mycluster
severity: warning
type: ceph_default
exp_annotations:
summary: "Network interface eth0 is down on cluster mycluster"
description: "A NIC used by one or more subsystems is in a down state"
# NVMeoFInterfaceDuplex - triggered on eth1 only
- interval: 30s
input_series:
- series: 'ceph_nvmeof_subsystem_listener_iface_info{duplex="full", device="eth0", cluster="mycluster"}'
values: '1+0x30'
- series: 'ceph_nvmeof_subsystem_listener_iface_info{duplex="half", device="eth1", cluster="mycluster"}'
values: '1+0x30'
promql_expr_test:
- expr: ceph_nvmeof_subsystem_listener_iface_info{duplex!="full"}
eval_time: 30s
exp_samples:
- labels: '{__name__="ceph_nvmeof_subsystem_listener_iface_info", device="eth1", duplex="half", cluster="mycluster"}'
value: 1
alert_rule_test:
- eval_time: 5m
alertname: NVMeoFInterfaceDuplex
exp_alerts:
- exp_labels:
duplex: half
device: eth1
cluster: mycluster
severity: warning
type: ceph_default
exp_annotations:
summary: "Network interface eth1 is not running in full duplex mode on cluster mycluster"
description: "Until this is resolved, performance from the gateway will be degraded"
# NVMeoFHighReadLatency
- interval: 30s
input_series:
- series: 'ceph_nvmeof_bdev_read_seconds_total{instance="node-1:10008",bdev_name="disk1",cluster="mycluster"}'
values: '0+1680x10 19800+3000x20'
- series: 'ceph_nvmeof_bdev_reads_completed_total{instance="node-1:10008",bdev_name="disk1",cluster="mycluster"}'
values: '0+286000x10 2980000+120000x20'
promql_expr_test:
- expr: label_replace((avg by(instance) ((rate(ceph_nvmeof_bdev_read_seconds_total[1m]) / rate(ceph_nvmeof_bdev_reads_completed_total[1m])))),"gateway","$1","instance","(.*):.*") > 0.02
eval_time: 10m
exp_samples:
- labels: '{gateway="node-1",instance="node-1:10008"}'
value: 0.025
alert_rule_test:
# negative test - latency is lower than 0.02s
- eval_time: 4m
alertname: NVMeoFHighReadLatency
# positive test - latency is higher than 0.02s
- eval_time: 15m
alertname: NVMeoFHighReadLatency
exp_alerts:
- exp_labels:
gateway: node-1
instance: node-1:10008
severity: warning
type: ceph_default
exp_annotations:
summary: "The average read latency over the last 5 mins has reached 10 ms or more on node-1"
description: "High latencies may indicate a constraint within the cluster e.g. CPU, network. Please investigate"
# NVMeoFHighWriteLatency
- interval: 30s
input_series:
- series: 'ceph_nvmeof_bdev_write_seconds_total{instance="node-1:10008",bdev_name="disk1",cluster="mycluster"}'
values: '0+1680x10 19800+3000x20'
- series: 'ceph_nvmeof_bdev_writes_completed_total{instance="node-1:10008",bdev_name="disk1",cluster="mycluster"}'
values: '0+286000x10 2980000+120000x20'
promql_expr_test:
- expr: label_replace((avg by(instance) ((rate(ceph_nvmeof_bdev_write_seconds_total[1m]) / rate(ceph_nvmeof_bdev_writes_completed_total[1m])))),"gateway","$1","instance","(.*):.*") > 0.02
eval_time: 10m
exp_samples:
- labels: '{gateway="node-1",instance="node-1:10008"}'
value: 0.025
alert_rule_test:
# negative test - latency is lower than 0.02s
- eval_time: 4m
alertname: NVMeoFHighWriteLatency
# positive test - latency is higher than 0.02s
- eval_time: 15m
alertname: NVMeoFHighWriteLatency
exp_alerts:
- exp_labels:
gateway: node-1
instance: node-1:10008
severity: warning
type: ceph_default
exp_annotations:
summary: "The average write latency over the last 5 mins has reached 20 ms or more on node-1"
description: "High latencies may indicate a constraint within the cluster e.g. CPU, network. Please investigate"