Replay
In the case of data retrieval failures for any data source, except for Splunk Observability, you can check this data source's event logs:
- The data source must be added with the direct connection method and, for Replay, using the Beta channel
- Event logs must be activated in advance for your data source
⛭ Datadog
If you exceed Datadog's API rate limit for SLOs with Replay, Replay will attempt to fetch data for 20 minutes. If all attempts fail, Nobl9 will create a standard SLO without historical data (that is, Nobl9 will collect data for such SLO from its creation).
⛭ ServiceNow Cloud Observability—missing data
ServiceNow Cloud Observability does not distinguish between missing and valid data with a 0 value in the stream. ServiceNow Cloud Observability considers these values equal in such cases and returns the 0 value.
⛭ New Relic
Before running Replay, check your New Relic data retention settings to ensure that all your historical data will be collected.
⛭ Prometheus
Since Prometheus is an on-site solution, if Replay keeps exceeding limits, remember to increase the limits on your side.
⛭ Incorrect source configuration
If you misconfigure your source (for example, incorrect credentials, incorrect query), Replay will attempt to fetch data for 20 minutes. When the last attempt is unsuccessful, the Replay job will fail. As a result, you will see the No data for this time period error in the UI:
If you enter an incorrect query for Datadog, Replay will fail immediately, and you will see the No data for this time period error in the UI.
⛭ Data loading time
Loading the historical data in Replay beta shouldn't exceed two hours (for extended periods of historical data retrieval). If your Replay process takes longer, contact Nobl9 support.