Alert policy threshold to be more than 120 Minutes

I want to create a condition under alert policy where I can observe application for 8 hours but the max threshold which we can set is 120 mins per condition.
How can we handle this situation and create policy for alerting bigger threshold ?

Hi @sameer - Unfortunately, since our alerts evaluation system happens on a minutely basis when the data comes in infrequently anything over 60 minutes gap will need to use the proposed workaround suggested below:

Relic Solution: Extending the functionality of NRQL alert conditions beyond a single minute

In addition, if the alert condition is based on a NRQL alert condition using count(). New Relic used to insert synthetic zeroes as a result for some queries, but ever since Streaming Alerts for NRQL conditions was introduced, synthetic zeroes are no longer inserted (the rules for when they were inserted were obtuse and opaque, so now you get exactly what the query returns).

Take a look at this article, which will explain why count() and uniqueCount() will never return a value of 0. The article also goes into a couple possible solutions depending on your use-case – these are new features which were also released with the Streaming Alerts Platform.

Depending on the situation you may need to set up a Loss of Signal (LoS) for the same duration as the threshold, and configure it to Open new "lost signal" violation when met. This will result in violations opening when the query stops returning numeric values and drops to 0/NULL or set up a Loss of Signal (LoS) for the same duration as the threshold, and configure it to Close all open violations when met. This will result in violations which close automatically, as you’d expect them to.

1 Like