Ask the Community
Groups
Performance counter alarms are delayed. - Connect IT Community | Kaseya
<main> <article class="userContent"> <p><strong>Problem</strong></p> <p>Although a performance counter monitor set is configured to create an alarm after 1 minute the alarm is generated much later.</p> <p>Example monitor set</p> <p><img src="/attachments/token/PK97nQrVaa6Rl9k3Ez0OOyVEL/?name=5-1.JPG" alt="5-1.JPG" width="700" class="embedImage-img importedEmbed-img"></img></p> <p>The Monitor set detects an alarm condition prior to 10:33 but the first alarm you receive is at 10:34</p> <p><img src="/attachments/token/XduAeucU2p4xV1qVpCozo8uMK/?name=5-2.JPG" alt="5-2.JPG" width="700" class="embedImage-img importedEmbed-img"></img></p> <p>The first alarm is created at 10:34 well over the 1 minute specified in the monitor set.</p> <p> </p> <p><img src="/attachments/token/DGYq4SIzuRCMCpianh2o7Ko5E/?name=5-3.JPG" alt="5-3.JPG" width="700" class="embedImage-img importedEmbed-img"></img></p> <p><strong>Cause</strong></p> <p>If the Interval is greater than 0 then two "Sample intervals" are required before Kaseya will know if the machine has been in an alarm condition longer than just at the time it was sampled. Kaseya then has to wait for the next "Sample" interval before it will knows if the machine has been in an alarm condition for a period of time. In this case that sample interval is 20 minutes so Kaseya has to wait 20 minutes for the next update. At this time Kaseya is able to calculate if the machine has been in an alarm condition greater than the "Duration" time or not and possibly creating an alarm.</p> <p> </p> <p><strong>Resolution</strong></p> <p>You can avoid this delay altogether by setting setting the "Delay" to 0 or you can reduce the time between each sample. </p> <p> </p> </article> </main>