How to Locate and Monitor Service Status for Splunk Observability Cloud Realms

Applicability

Description

While the Splunk Observability Cloud platform is designed for high availability, if on the rare occasion, users encounter intermittent accessibility issues, delayed data ingestion, or functional limitations within the web interface. These symptoms can include connection timeouts, 503 Service Unavailable errors, or minor delays in chart and detector updates. It is essential for a user to verify whether the issues are isolated to their specific environment or if they are part of a broader, known service incident affecting their organisation.

Investigation

To determine if a user is experiencing a known service incident, the following steps should be performed:

1. Identify the Realm: The realm is typically indicated in the URL when logged into the Splunk Observability Cloud interface (e.g., us0, eu0).
   
   
2. Access the Realm-Specific Status Page: Navigate to the dedicated status page using the following URL structure: https://status.<your_realm>.signalfx.com/
   
   
3. Verify Incident Status: If the status page does not show an active incident, the issue may be local to the user's network or specific to their local configuration. If the status page shows "System Operational" but the user is still experiencing issues, they should verify their local network connectivity or contact support for further investigation.
   
   

Resolution

To ensure a user is viewing the most accurate information regarding their environment, please follow these steps:

1. Determine the Correct URL

Each realm has a unique status page. A user must ensure they are viewing the status page specific to their organisation's deployment.

• For example, if a user is in the us0 realm, they should bookmark: https://status.us0.signalfx.com/
• Examples of other realms include au0, eu0, us1, jp0, etc.

2. Review Incident Details

Once on the correct page, review the "Incident History" or "Active Incidents" section. If an incident is listed, it will provide:

• The scope of the impact (e.g., Charts and Detectors Delayed).
• The current status (e.g., Investigating, Monitoring, or Resolved).
• Expected timeframes for resolution or recovery.

3. Subscription to Updates

To stay informed during an incident, users can utilise the "Subscribe to Updates" button located on the status page. This allows the user to receive email or SMS notifications directly from the operations team whenever an incident status changes.

If the status page indicates that an incident is resolved, but the user continues to experience issues, please clear the browser cache or attempt to access the interface via an incognito window to rule out local browser-related conflicts. If the problem persists, please open a new support case and reference the relevant incident ID if applicable.