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.
Important note: It is not possible to change the intervals mentioned below.
|
Alert Type |
Minimum Time for Alert | Maximum Time for Alert |
|
Agent Comes Online (Availability alert) |
10 sec |
|
|
Agent Goes Offline (Availability alert) |
90 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 |
||
The values provided below are related to the Devices page. When accessing an Agent directly, these values will update in real-time.
| Agent Information | Update Time |
| Alerts | Real-time |
| Availability | |
| Relations | |
| Public IP Address | |
| Available patches | 1 hour |
| Last Login | 12 hours |
| Pending reboot | 12 hours or after reboot |
| Last reboot | 12 hours or after reboot |
