PRTG Manual: Notifying
PRTG keeps you or other responsible persons informed about the status of the network. There are several methods that you can use to stay up to date.
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 to notify you of issues (for example, email, SMS, push messages, and others). After you create 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.
For more information, see section Notifications and section Setting Up Notifications Based on Sensor Limits: Example for a step-by-step guide.
In a sensor's channel 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 a Down status) to a Down status whenever bandwidth values are measured that you consider critical. This sensor then shows up in the alarms list.
The alarms list shows all sensors that are in a Down, Down (Partial), Down (Acknowledged), Warning, or Unusual status. Sensors in other states (for example, Up, Paused, or Unknown) do not appear here. This is useful for keeping track of all irregularities in your network.
For more information, see section Alarms.
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 documented, you can use this data to check exactly if your setup works as expected.
For more information, see section Logs.
The tickets list shows items with important system information or action steps for you to take. You should view every ticket and take appropriate action. By default, an email is sent to the administrator for every new ticket that is created by the system or a user. If a ticket is assigned to a specific user, this user receives an email by default.
For more information, see section Tickets.