No data anomaly

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

The automatic No data anomaly identifies an SLO objective that has stopped reporting data for an extended period. It is available with automatic data anomaly detection in Nobl9 Enterprise Edition.

This rule is separate from the manually configured No data alert. The manual rule can notify selected alert methods and lets you choose its waiting time for an SLO. The automatic rule uses centrally managed settings and creates a data anomaly annotation.

How detection works

By default, Nobl9 detects this anomaly after an objective has reported no points for one week. The observation period starts after the last received data point. When data resumes, Nobl9 resolves the anomaly.

No data detectionThe gap begins after the last point. Detection occurs after one week without data, and the next point resolves the anomaly.

Reported value

Setting	Automatic default
Observation period	1 week
Cooldown	None

Query timing

Query delay and other query parameters affect when Nobl9 can confirm that data is missing. SLO charts use timestamps from the data source, while annotation creation reflects when Nobl9 confirms the anomaly.

What to investigate

1. Check the data source connection status and event logs.
2. Run the configured query directly against the data source for the affected period.
3. Check query interval, timeout, and delay settings against the expected data density.
4. Verify data source credentials, URLs, permissions, and network access.
5. Check the data source's status page and API rate limits.

For source-specific checks, see Data anomaly troubleshooting.

API access

Query No data anomalies with the Anomalies API and anomalyTypes: ["NoData"]. Retrieve continuously detected annotations with the Annotations API and category=NoDataAnomaly.