Skip to main content

Replay and SLI Analyzer troubleshooting

Reading time: 0 minute(s) (0 words)

In this guide, you will find solutions to common issues that may arise when using Replay or SLI Analyzer features.

To identify and address root causes effectively, check event logs for the affected data source. Note:

  • The data source must be connected using the direct connection method.
  • Ensure event logs are activated for the data source in advance.

⛭ Replay is unavailable​

If the "Run Replay" option is inactive, consider the following:

  1. Unsupported data source.
  2. Maximum period set to zero.
    • The Maximum period for historical data retrieval in your data source settings might be set to 0. Resolution: Increase the maximum period to activate Replay.

⛭ ServiceNow Cloud Observability—missing data​

ServiceNow Cloud Observability treats missing data points with a 0 value as valid data. This can lead to inaccuracies in Replay results when distinguishing missing from valid data.

Recommendation: Validate the integrity of the data stream within ServiceNow to ensure proper data handling.

⛭ Prometheus API Rate Limits Exceeded​

Prometheus may frequently hit API rate limits during Replay as it operates as an on-site solution.

Resolution: Increase the API rate limits configured in your Prometheus setup. This can improve Replay performance by allowing more requests to be processed.

⛭ Cannot create an analysis for a data source​

For SLI analyses, the following conditions must be met:

  1. You must have one of the following project-level roles in the project that contains the data source:
    • Project owner
    • Project editor
    • Integrations user
  2. Historical data retrieval must be enabled for the data source, with a minimum retrieval period of 5 minutes.

Read more about setting up historical data retrieval and supported data sources.

⛭ Missing data in SLI Analyzer​

When data appears missing during SLI analysis, it can be due to:

  1. Retention policy of the data source.
    • Ensure the data source retains data for the requested periods. Refer to the data source's retention policy.
  2. Access restrictions.
    • Certain data sources may block traffic to Nobl9. Configure an allowlist for Nobl9 IP addresses.
IP addresses to include in your allowlist for secure access

If you're using app.nobl9.com instance:
  • 18.159.114.21
  • 18.158.132.186
  • 3.64.154.26
If you're using us1.nobl9.com instance:
  • 34.121.54.120
  • 34.123.193.191
  • 34.134.71.10
  • 35.192.105.150
  • 35.225.248.37
  • 35.226.78.175
  • 104.198.44.161

⛭ Empty SLI values distribution chart​

If the SLI Analyzer displays an empty values distribution chart:

  1. Sparse or homogenous data.
    • Verify that your data source includes enough variations within the requested timeframe.
  2. Inappropriate time window.
    • Experiment with different graph time windows for better visualization.

⛭ Failed import​

When an SLI analysis returns an Import failed error, the root cause can often be identified in the event logs.

Typical issue: The logs may show 0 under the # of Affected SLOs column, indicating that the failure did not impact any configured SLOs.

⛭ Reliability burn down over 100%​

This issue arises when a ratio metric in an SLI Analysis is misconfigured:

  • Ensure that the data count method is set correctly (e.g., non-incremental for non-cumulative metrics).
Note

The data count method cannot be changed after pressing the Import Data button.

On this page