Incident Library
Applied filters Root causeCapacity exhaustionSymptomLoad imbalanceOrganisationMongoDBClear allEvery case under the filters, with no sentence; newest first.
Suggested filters Search, and the values found in your words appear here.

Graph

  • Root cause
  • Component
  • Symptom
  • Contributing factor
  • Case

Cases1 case

1 to 1 of 1

  1. Symptoms

    On 7 October 2025 MongoDB reported a delay in the metric ingestion pipeline of MongoDB Atlas and Cloud Manager. Metrics in Atlas dashboards arrived late or went missing, Host Down alerts did not fire, and Atlas cluster management operations such as provisioning and resizing were delayed, while customer clusters themselves stayed healthy and available.

    Trigger

    The rollout of an updated internal software version caused a temporary spike in resource demand on the internal database cluster.

    Root cause
    Component
    Contributing factor
    Remediation
    • Took corrective actions to stabilise the system and monitored their effect
    • Implemented a fix and monitored the results until the incident was resolved
    Action items
    • Shard the collections with concentrated load to spread traffic over more nodes
    • Optimise inefficient queries
    • Provision additional infrastructure capacity for higher traffic
    • Refine capacity planning to anticipate future load spikes, using metrics from this event
    • Redesign software rollouts to account for the predictable rise in resource demand during a rollout
    • Keep monitoring how the sharding and query changes resolve the hotspots
    • Expand the detection of elevated load conditions for faster anomaly detection and response
Check your cluster for this

This case involves Database. kubegap audits a Kubernetes cluster for gaps like these, read-only, from Claude Code or Codex; its checks cite public reports like the ones in this library.

By root cause1