I want to share that, over the course of the next month, we are releasing official support for “loss of signal detection” for NRQL Conditions. Loss of Signal configuration allows you to set an expiration duration, in wall clock time, from the time that we received the last data point. Once that time expires, we will identify that signal as being lost. Once that happens, we will allow for 2 actions:
- close all open violations
- create a new violation (and resultant notification) for “Loss of Signal”
The maximum expiration duration we will support to start with is 48 hours. Therefore, you should be able to use this feature for being alerted if infrequent jobs do not report data within the expected time frame. If you expect a service to report every 6 hours, you can set an expiration duration of 6 hours and 15 minutes (for example), and be notified if that signal is lost.
After we release this, we will reassess this use case to determine if another method is still required.
We should have Loss of Signal Detection completely by end of July 2020, and then proceed to begin the rollout of Gap Filling capabilities.
Product Manager - AI Ops