What problem are you trying to solve?

Focus on the what and why of the need you have, not the how you'd like it solved.

We are observing an issue with false positive alerts related to the "Replication Oplog Window Minimum Threshold: 24 hours" on newly provisioned MongoDB replica sets.
As per documentation (e.g., MongoDB Oplog Sizing Guide), a minimum oplog window of 24 hours is recommended for cluster stability and recovery.
Our monitoring setup, which includes Ops Manager, is configured to alert if the oplog duration falls below this threshold.
The problem arises when a new MongoDB cluster is provisioned. For example, if a cluster has only been active for 2-3 hours,
its actual oplog duration will naturally be 2-3 hours, not yet having accumulated 24 hours of operation history.
This inevitably triggers an alert stating that the oplog window is below the 24-hour minimum threshold.

While these alerts are technically correct based on the raw metric, they represent false positives in the context of a new cluster's lifecycle.
This leads to significant alert fatigue, potentially masking genuine issues, and creates unnecessary operational overhead for our on-call teams who must triage and dismiss these expected alerts.

What would you like to see happen?

Describe the desired outcome or enhancement.

No false positive alerts related to the "Replication Oplog Window Minimum Threshold: 24 hours"

Why is this important to you or your team?

Explain how the request adds value or solves a business need.

Effort reduction and attaining false alerts and tickets .

What steps, if any, are you taking today to manage this problem?