About the behavior of "Interval of action"
Answered
Hello,
If "Interval of action" is set for Action, the event that occurred during the interval will be executed at the end of the interval as shown below.
Is there a way to prevent the action at the end of Interval from running?
There are cases where you do not want the action to be executed at the above timing, such as when "Do HTTP request" is specified for the action.
-
Hi Daiki Kato,
No, when an interval of action is used, there will be always a second action, if during the interval another event occurred.
If you set the interval to instant, the actions will be executed when the even occurs.
Can you be more specific about the case where you do not want the action to be executed at the above timing?
0 -
Hi Norman,
Thanks for your quick reply. For example, assume the following cases.
1. Notify another server with "Do HTTP request" when an anomaly occurs.
2. Assume that events continue to enter while anomaly occur. (It is notified by "Analytics Event" etc.)
3. Considering the amount of traffic and the load on the server, we would like to limit the frequency of executing "Do HTTP request" to about once every 20 seconds.
4. Do not notify the server after the anomaly is resolved.0 -
Hi Daiki Kato,
I kind of understand what you want, but I'm not sure how we can determine if an event or anomaly should be ignored or be sent after the interval of action?
If I understand your case correctly, you receive too many false positives, but this typically means that it should be resolved at the source.
E.g. if an analytic event sends multiple events for the same event, configuration should be changed at the source to prevent false positives as much as possible.
For example, sometimes Enter a Region might be a better option than a Cross line event or vice versa.
And is traffic really an issue? An HTTP request is just a few KB and hardly should be a bottleneck on any connection.
0 -
Hi Norman,
Thank you for your reply. I would consider processing on the source side.
As for the traffic, I assumed the unwise server would get camera snapshots and videos. If the server side behaves smartly, there is no problem.0 -
I have several use cases where I would prefer NX Witness to suppress further notifications after the first intrusion detection trigger for a specified period of time.
At present, the Interval of Action setting causes a notification to be sent at the first trigger and then again after the set interval — even if multiple triggers occur in the meantime. For example, if the interval is set to 1 hour, a notification is sent immediately, and then again exactly an hour later if intrusion detection continues or is retriggered, regardless of any new activity in between.
My use cases include:
- Remote sites where maintenance staff might be moving around for an extended time (e.g., an hour). We only want a single notification when they first arrive, not repeated alerts as they pass by the camera multiple times.
- Walking tracks where tour groups pass by. Occasionally, slower individuals trigger new detections after the main group has gone through. We would like to ignore these stragglers for a short window of time (e.g., 2–5 minutes).
Other VMS platforms offer a setting like "Time between emails" that allows you to suppress notifications for a defined time window after the first one. This would be extremely helpful in reducing noise and avoiding alert fatigue, especially in scenarios where constant movement is expected for a short time.
Could this type of functionality be considered in future updates, or is there a recommended workaround?
0 -
Hi Brett C,
To ensure your voice is heard, and your suggestions are considered by our Product Team, I encourage you to visit our Feature Feedback section in our community and submit your feedback there. This section of our community is specifically monitored by our Product Team, and it's where you can engage with others, vote on feature requests, and share your ideas for new features or improvements.
You can access the Feature Feedback section through THIS link.
0
Please sign in to leave a comment.
Comments
6 comments