Use the following information to help troubleshoot anomaly detection.
Why do I see the message "There is not enough data at this time for contributing analysis."?
You might see a blank contribution analysis results with the message "There is not enough data at this time for contributing analysis." Here are some cases when this could occur:
- The system compares all the other related metrics and dimensions on anomaly dates with the data on normal dates (within 30 days). It's possible that there is insufficient data on either date, so the system is not able to figure out which factor is changed.
- If all related metrics and dimensions are not changed, the system does not regard them as contribution factors, to avoid listing non-meaningful results.
For newly created events and metrics, anomaly detection provides results after 14 full days of data collection. If you enable anomaly detection on events that existed for more than 14 days, the analysis should be available in ten to thirty minutes. After the initial calculations, anomaly detection is updated only once each day. Also, the missing value within the data should not be larger than 50%.
In some scenarios, for example when a single metric with many anomaly points and with metric dimensions that have many distinct values, anomaly detection can take longer than 30 minutes to display data.
Anomaly detection recalculates when you change contributing factors, or when you enable anomaly detection on a different metric. Also, if you remove metric on which anomaly detection runs, delete a report, or delete a dashboard, old anomaly detection data is removed.
Why do I only see the daily point?
In a normal report, I selected hourly breakout and monthly breakout. Why does the anomaly view still display the daily point?
Anomaly detection is currently supported only at a daily level.
Why don't I see yesterday's anomaly detection data?
I enabled a metric on anomaly detection. But why isn't yesterday's data showing yet?
The system needs to ensure that yesterday's data is completely processed, so the analysis work for yesterday's data starts after 8:00AM today. The scheduled job runs in intervals of 4 hours, so yesterday's data is normally calculated between 8:00AM and 12:00 noon.
After I enabled anomaly detection, why are only 6 months’ worth of line points displayed?
In a normal report, there is one year of data. Why am I only seeing data for six months?
When initially doing anomaly detection on one metric, the system only calculates anomaly points and analyzes contribution factors on the dates within the range of 180 days. After that, when there is new data incoming for new days, it automatically calculates when the new day is complete.
When I try to enable anomaly detection on a metric, why do I get the error "You have exceeded the maximum number of metrics allowed for anomaly detection. Deselect metrics to continue."?
You can enable anomaly detection on up to 20 metrics.
Workspaces that include reports with anomaly detection enabled and reports that include metrics with Anomaly Detection enabled are marked with blue triangle icon. You can keep track of the number of metrics enabled by hovering your mouse over the blue triangle icon for workspaces and reports listed in the navigation.
Administrators and SupportUsers can track the number of Anomaly detection metrics currently in use by the organization from the Admin Workspaces.
When I click View sessions, why are no sessions listed?
When I click View sessions, why are no sessions listed?
To resolve this issue, complete the following steps:
- Check the session retention date. If the anomaly date is outside of the retention date, no session can be queried.
- Check if the metric and dimension of the contribution item exist because contribution analysis results keep the original result even if the metric or dimension is deleted afterward. However, if one of them is deleted, no session can be queried.