Bug 2207713 - Create RBD mirror monitoring related alerts in Ceph mixins [NEEDINFO]
Summary: Create RBD mirror monitoring related alerts in Ceph mixins
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RBD-Mirror
Version: 6.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 6.1z2
Assignee: arun kumar mohan
QA Contact: Sunil Angadi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-05-16 15:39 UTC by Juan Miguel Olmo
Modified: 2023-08-03 08:31 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:
sangadi: needinfo? (amohan)


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ceph ceph pull 50132 0 None open ceph-mixin: Add RBD Mirror monitoring alerts 2023-05-16 15:44:58 UTC
Red Hat Issue Tracker RHCEPH-5820 0 None None None 2023-05-16 15:39:31 UTC
Red Hat Issue Tracker RHCEPH-6677 0 None None None 2023-05-16 15:40:40 UTC

Description Juan Miguel Olmo 2023-05-16 15:39:31 UTC

Comment 1 RHEL Program Management 2023-05-16 15:39:39 UTC
Please specify the severity of this bug. Severity is defined here:
https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity.

Comment 2 Juan Miguel Olmo 2023-05-16 15:42:23 UTC
As monitoring user, we will need a new set of alert to reflect any problem in the rbd mirroring process. The alert should raise any time than an image is not being replicated properly, and inform about the problem and possible solution.

The list of alerts and description is:
CephRBDMirrorImagesPerDaemonHigh:
Number of image replications are now above 100

CephRBDMirrorImagesNotInSync
Some of the RBD mirror images are not in sync with the remote counter parts.

CephRBDMirrorImagesNotInSyncVeryHigh
Number of unsynchronized images are very high

CephRBDMirrorImageTransferBandwidthHigh:
The replication network usage has been increased over 80% in the last 30 minutes.


Note You need to log in before you can comment on or make changes to this bug.