Splunk Observability Cloud JP0 incident

Splunk APM Trace Data Ingestion Delayed

Major Resolved View vendor source →

Splunk Observability Cloud JP0 experienced a major incident on August 12, 2024 affecting Splunk APM Trace Data and Splunk APM Business Workflows and 1 more component, lasting 16m. The incident has been resolved; the full update timeline is below.

Started
Aug 12, 2024, 08:29 PM UTC
Resolved
Aug 12, 2024, 08:45 PM UTC
Duration
16m
Detected by Pingoru
Aug 12, 2024, 08:29 PM UTC

Affected components

Splunk APM Trace DataSplunk APM Business WorkflowsSplunk APM API

Update timeline

  1. investigating Aug 12, 2024, 08:29 PM UTC

    A degradation in the the Splunk APM data ingestion pipeline is causing delays in processing and storage of trace data leading to issues with loading Trace Analysis and Exemplars.

  2. identified Aug 12, 2024, 08:32 PM UTC

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

  3. monitoring Aug 12, 2024, 08:36 PM UTC

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

  4. resolved Aug 12, 2024, 08:45 PM UTC

    This incident has been resolved.