You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@MalloZup My suggestion is that we could split the metrics in a way where the values represent the states and the label really identify the attributes for filtering (disk, nodes, etc). For example:
# Use 0=Out of Sync, 1=UptoDate, 2=Syncing
ha_cluster_drbd_resource_disk_state{resource_name="1-single-0", role="primary", volume="0"} 1
# Use 0=Out of Sync, 1=UptoDate, 2=Syncing
ha_cluster_drbd_resource_disk_state{resource_name="1-single-0", role="primary", volume="0"} 1
ha_cluster_drbd_resource_written_bytes{resource_name="1-single-0", role="primary", volume="0" } 536513
this will follow same schema as 1)
2) ha_cluster_drbd_resource_connection_state{resource_name="1-single-0", role="primary", volume="0" peer-node-id="2" peer-role="Secondary"} 1
metric:
ha_cluster_drbd_resource{resource_name="1-single-0", role="primary", volume="0", disk-state="uptodate", replication-state="etablished", peer-disk-state"uptodate"}
ha_cluster_drbd_resource{resource_name="vg2", role="secondary", volume="0", disk-state="uptodate" replication-state="etablished", peer-disk-state"uptodate"}
ha_cluster_drbd_resource{resource_name="vg2", role="secondary", volume="1", disk-state="outdated" replication-state="etablished", peer-disk-state"uptodate"}
drbdsetup status --json
The text was updated successfully, but these errors were encountered: