Splunk Observability Cloud JP0 incident

Splunk APM Troubleshooting MetricSets Delayed

Minor Resolved View vendor source →

Splunk Observability Cloud JP0 experienced a minor incident on April 15, 2025 affecting Splunk APM Troubleshooting MetricSets and Splunk APM Trace Data and 1 more component, lasting 1h 39m. The incident has been resolved; the full update timeline is below.

Started
Apr 15, 2025, 07:45 AM UTC
Resolved
Apr 15, 2025, 09:25 AM UTC
Duration
1h 39m
Detected by Pingoru
Apr 15, 2025, 07:45 AM UTC

Affected components

Splunk APM Troubleshooting MetricSetsSplunk APM Trace DataSplunk APM Tag SpotlightSplunk APM Business Workflows

Update timeline

  1. investigating Apr 15, 2025, 09:25 AM UTC

    A degradation in the performance of the Splunk APM trace processing pipeline is causing Troubleshooting MetricSets to be delayed by more than five minutes. As a result, the APM Troubleshooting experience, service maps and Tag Spotlight do not have access to the most recent data. The processing of metrics for Business Workflows, which also depends on this pipeline, are equally delayed. Trace data ingest is not impacted at this time; service-level and endpoint-level Monitoring MetricSets and the detectors built from them are also not impacted.

  2. identified Apr 15, 2025, 09:27 AM UTC

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

  3. resolved Apr 15, 2025, 09:30 AM UTC

    This incident has been resolved.