Splunk Observability Cloud JP0 incident

Splunk APM MetricSets Delayed

Minor Resolved View vendor source →

Splunk Observability Cloud JP0 experienced a minor incident on June 5, 2025 affecting Splunk APM Monitoring MetricSets, lasting 38m. The incident has been resolved; the full update timeline is below.

Started
Jun 05, 2025, 11:47 PM UTC
Resolved
Jun 06, 2025, 12:26 AM UTC
Duration
38m
Detected by Pingoru
Jun 05, 2025, 11:47 PM UTC

Affected components

Splunk APM Monitoring MetricSets

Update timeline

  1. investigating Jun 06, 2025, 12:22 AM UTC

    A degradation in the performance of a key backend component of Splunk APM is causing both Troubleshooting and Monitoring MetricSets to be delayed by more than five minutes. No data is being dropped at this time but data for the APM Troubleshooting page and Tag Spotlight experience, as well as metrics created from traces and APM detectors are all delayed.

  2. identified Jun 06, 2025, 12:23 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jun 06, 2025, 12:23 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jun 06, 2025, 12:26 AM UTC

    This incident has been resolved.