Sentry-go KnowledgeBase Article

Sentry-go KnowledgeBase
Title	Printer and/or process-based alerts are triggered much more often than the scan interval specified.
Applies To	Sentry-go Monitoring, v5.x & v6.x

Problem: Whilst running the monitor, you notice a number of alerts triggered by the printer and/or process monitors even though a higher scan interval is specified. If you monitor real-time activity, you notice these monitors performing scans much more frequently than expected. Cause: This behavior can happen when shadow events are enabled. Shadow process & printer events allow the monitor to perform its checks when conditions that might affect thos checks occur, even between scans - e.g. the starting of a process or the addition of a new print job. However, this in turn causes the monitor to perform all the component's checks and hence these tests they are performed more than might be expected. Solution: This is by design - in that there are often times when it is desirable and hence the benefit of enabling shadow events. However, where the additional checks will not benefit from this, you can stop the alerts being continually triggered by configuring them not to be verified for X minutes after the initial alert has been raised. This is sepcified on the "Alerts" tab for the process or printer check (the default is 0, indicating that the alert is always triggered).