Skip to main content

Smart Alert FAQ

info

When alert behavior does not match expectations, first verify the detection interval, trigger conditions, data availability, and notification strategy for the affected rule.

Why can an alert arrive later than expected after I configure a rule?​

Check the rule's Continuous Trigger Count and Data Delay settings. A rule configured to trigger after consecutive matches waits for each required detection cycle, and a data-delay offset means it evaluates an earlier, stable data window. See Monitor Principles for the execution model.

Why is a Data Gap alert triggered when data exists?​

First check whether the data was written during the complete detection interval and whether the effective scope or filter tags exclude it. When reporting is delayed, enable and tune Data Delay before relying on the result. See Monitor Principles.

Why do several alerts result in one notification, or one alert result in repeated notifications?​

Check the aggregation rule and repeat-notification settings in the associated Notification Strategy. Aggregation can merge multiple events within its window, while repeat notifications continue for alerts that remain unrecovered.

Does a blocking strategy stop alert events from being generated?​

No. A Blocking Strategy intercepts alert notifications only; alert events continue to be generated and recorded.