Changes / Datadog / Delayed Processes data
Datadog: Major incident: Delayed Processes data
Summary
Datadog reported a major degradation in Metrics and Infra Monitoring: increased Processes data latency caused possible Process Monitoring data delays or gaps, and related monitors were temporarily disabled to prevent spurious alerts. It started at 2025-12-12 21:49 UTC and lasted 1 h 54 min, resolving at 2025-12-12 23:43 UTC after a fix was implemented.
Machine-written from the diff below (Sol; type: incident degradation). Check the diff before relying on it.
Major incidentLabel: degradation (model (Jev), 100%)Changed Detected Source: stspg.io (opens in new tab)
What changed
Before: not present
After: Delayed Processes data
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2025-12-12 21:49 UTC
Before: not present
After: 2025-12-12 23:43 UTC
Before: not present
After: Metrics and Infra Monitoring
Before: not present
After: We are investigating increased latency processing Processes data.
As a result of this issue, some users may see delays or gaps for data based on Process Monitoring.
To prevent spurious alerts, we have temporarily disabled monitors based on this data.
Before: not present
After: We are continuing to investigate this issue.
Before: not present
After: The issue has been identified and a fix is being implemented.
Before: not present
After: A fix has been implemented and we are monitoring the results.
Before: not present
After: This incident has been resolved.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Delayed Processes data (this change) Datadog reported a major degradation in Metrics and Infra Monitoring: increased Processes data latency caused possible Process Monitoring data delays or gaps, and related monitors were temporarily disabled to prevent spurious alerts. It started at 2025-12-12 21:49 UTC and lasted 1 h 54 min, resolving at 2025-12-12 23:43 UTC after a fix was implemented. | Major incident |