Fix Backup Oplog Issues
On this page
Cloud Manager will no longer support Automation, Backup, and Monitoring for MongoDB 3.6 and 4.0 after August 30th, 2024. Please upgrade your MongoDB deployment or migrate to Atlas.
- OAuth 2.0 authentication for programmatic access to Cloud Manager is available as a Preview feature.
- The feature and the corresponding documentation might change at any time during the Preview period. To use OAuth 2.0 authentication, create a service account to use in your requests to the Cloud Manager Public API.
The Cloud Manager backup service has not received an oplog from the MongoDB Agent for at least an hour.
Alert Conditions
You can configure alert conditions in the project-level alert settings page to trigger alerts.
To learn more about the alert condition, see Backup oplog is behind.
Common Triggers
MongoDB Agent is down.
MongoDB Agent is overloaded.
MongoDB Agent can't reach the replica set.
MongoDB Agent can't reach or successfully send data to Cloud Manager.
MongoDB Agent is continuously restarting.
Fix the Immediate Problem
Check the MongoDB Agent logs in Cloud Manager and on the MongoDB Agent host to find out which of these occurred.
Implement a Long-Term Solution
Manage your MongoDB Agent settings.
Monitor Your Progress
View the {mdbagent+} status on the Agents tab to monitor your progress.
To learn more, see View Agent Status.