CompaniesDigitalOceanIncidents
DigitalOcean: Monitoring Alerts for MongoDB Cluster
Timeline of updates
- resolved
Resolved After further investigation, our Engineering team has discovered that monitoring alerts, other than disk usage, have been triggering correctly for MongoDB clusters, but have been missing cluster information, such as the name of the cluster in the email subject line. Additionally, there is a known issue with disk usage alerts for MongoDB clusters that has been present since the launch of the product. A small number of clusters are impacted. We apologize for any miscommunication and misunderstanding. At the outset of this incident, with the data available, we believed this to be much more impactful. Our Engineering team will work to correct the missing cluster information in triggered alerts to improve the customer experience. Longer-term work is planned to allow for successful disk alerts for MongoDB clusters as well. Given this, we’ll close this public incident. If you have any questions or concerns, please reach out to Support from within your account. Thank you. Mar 17, 2023 - 16:15 UTC - Identified As of 13:35 UTC, our Engineering team has identified the issue with Monitoring alerts for MongoDB Clusters and is working on a fix. We will post an update as soon as additional information is available. Mar 17, 2023 - 13:51 UTC - Investigating Our Engineering team is investigating an issue with Monitoring alerts for MongoDB Clusters in all region. During this time, alert policies may be delayed or fail to trigger their configured notification options. We apologize for the inconvenience, and we'll share an update once we have more information. Mar 17, 2023 - 12:47 UTC - This incident affected: Regions (Global) and Services (Monitoring).
From DigitalOcean’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.digitalocean.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by DigitalOcean, started 2023-03-17 20:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Monitoring Alerts for MongoDB Cluster
- Vendor
- DigitalOcean
- Date
- URL
- https://rewindex.com/company/digitalocean/incidents/ckq7nkn038zp
DigitalOcean profileRecent DigitalOcean incidentsAll outages on March 17, 2023DigitalOcean in March 2023MarkdownJSON