Every night at 3:04am we get an anomaly detection alert for “Non-web throughput was much different than normal”. See link and image below. Our nightly jobs run at 3:00am every day. Normally anomaly detection is good at comparing the current metrics to an appropriate baseline (e.g. Sunday to previous Sundays, middle of the night to previous middle of the nights), however in this case for weeks our metrics show the same spike for ~5 minutes at 3:00am every day and it continue to alert us that it is an anomaly.
Our question is: What can we do to tell/train New Relic anomaly detection that “Non-web throughput…” is NOT an anomaly at ~3am. Looking at the screenshot below we can click No for “Keep detecting anomalies like this?”, but we WANT to detect “Non-web throughput” anomalies, it’s just not an anomaly at 3am. Does clicking No only apply to 3am or will it turn of “Non-web throughput” anomaly detection for this project?
