PRTG Manual: Notifying
PRTG Network Monitor keeps the administrator or other responsible persons informed about the current status of the network. There are several methods how the administrator can stay up to date.
This is the most powerful information tool. Whenever PRTG discovers downtime, an overloaded system, threshold breaches (for example, a disk runs full), or similar situations, it can send a notification. Notifications use various methods with which you can be notified (for example, email, SMS, push messages, and others). After creating notification templates in the system settings, you can select them on the Notification Triggers tab of probes, groups, devices, and sensors, as well as of the root group.
See section Notifications for more information and Setting Up Notifications Based on Sensor Limits: Example for a step-by-step guide.
In a sensor channel's settings, you can set limits to change the status of the sensor when certain limits are breached. This way, you can set, for example, a traffic sensor (typically never in an error status) to Down status whenever bandwidth values are measured that you consider critical. This sensor will then show up in the alarms list.
The alarms list shows all sensors that are currently in a Down, Down (Acknowledged), Warning, or Unusual status. This is useful for keeping track of all irregularities in your network. In the table list, you can sort the items by clicking on the column's header items.
See section Alarms for more information.
In the logs list, the logfile with all monitoring events is shown. In a typical setup, a huge amount of log data is produced. As the activity of every single object is minuted, you can use this data to check exactly if your setup works as expected.
See section Logs for more information.
The tickets list shows items with important system information or action steps for the administrator to take. You should view every ticket and take appropriate actions. By default, an email is sent to the administrator for every new ticket that is created by the system or another user. If a ticket is assigned to a specific user, this user will get an email by default.
See section Tickets for more information.