Log in

How can we help?

  1. Atera Support
  2. Atera MSP
  3. Remote Monitoring and Management (RMM)
  4. Remote Monitoring and Management (RMM) - Become an Expert
Help Center
    Was this helpful?
    5 out of 7 found this helpful

    Alert Time Intervals

    The Atera agent, the backbone of the Atera monitoring system, monitors the availability, performance, and health of the workstation\server, at regular intervals and securely communicates back to the cloud. The reporting intervals are based on extensive big data analysis, ensuring optimal notification timing. This article outlines the time intervals used by Atera when monitoring different types of system events that trigger Alerts. The table below displays the most common Atera alert types, and the time intervals within which you can expect to receive those alerts.   

     Alert Type

    		  Minimum Time for Alert  Maximum Time for Alert

     Agent Comes Online

     10 sec

     3 min

     Agent Goes Offline

     92 sec

     5 min

     Threshold with Persistence Check *

    As configured in the  threshold item (adjustable  time period)

    As configured in the threshold  item (adjustable time period),  plus up to 2 minutes

     

     Threshold without Persistence Check **

     2 min

     5 min

     Device Availability

     2 min

     5 min

     Resolution Time for Alerts

     2 min

     5 min

     * Threshold for the following:

     CPU Load

     Memory Usage

     CPU Temperature

     Motherboard Fans

     Motherboard Temperature

     Hardisk Temperature

     ** All other thresholds

     

    Agent Information Update Time
    Software 1 min
    Security
    Hardware
    Last Logged User
    Last Seen 30 min
    Last Reboot Time
    IP Address

     

    Manually Updating the Time Interval

    The reg key below provides an option to set the monitoring interval for Agent Online / Offline monitoring (the first 2 items in the table above).

    To update the monitoring interval:

    1. Navigate to the following Registry path: HKEY_LOCAL_MACHINE\SOFTWARE\ATERA Networks\AlphaAgent 

    2. Add DWORD key HeartBeatInterval (the base should be in Decimal)

    3. Set the value to 90 (30 seconds is the minimum time value).

    4. Restart the AteraAgent service

    Note: For flaky internet connections, we recommend the interval to be updated to a minimum of 5 minutes to allow more time for the agent to connect with the main server and run as expected. 

    The above steps can also be automated in order to run the commands remotely via CMD (open as administrator):

    REG ADD "HKEY_LOCAL_MACHINE\SOFTWARE\ATERA Networks\AlphaAgent" /f /v HeartBeatInterval /t REG_DWORD /d 90 
    sc stop AteraAgent && sc start AteraAgent

     

    For more on alerts, check out these articles:

     

     

     

    Still have a question? Contact us
    Ilana Wolf

    Related articles