How To Alert If Service Fails With Prtg Network Monitor

PRTG Transmission: Alerts

Alerts are an important role of monitoring that informs yous when there are bug, when values exceed thresholds, or when a sensor status has inverse, for example. PRTG offers many means to alert you about your monitoring data like internal sensor alerts, limits, and lookups. You lot can also create custom alerts and define notification triggers every bit extensions to alerts. If a sensor does not have preconfigured limits, you can besides configure them so that you are notified when something is wrong.

In this department:

Internal Sensor Alerts
Standard Limits for Channels
Standard Lookups for Channels
Modifying a Standard Lookup: Example
Notification Triggers as Extensions to Alerts
Create Notification Triggers to Alert You lot When a Value Changes
Create Notification Triggers to Match Your Limits/Lookups (State Based)

Internal Sensor Alerts

Some sensors display internal alerts when there are errors. These default alerts range from disconnected probes to socket or timeout errors. For example, the HTTP sensors prove preconfigured internal alerts co-ordinate to certain HTTP status codes.

There are also sensors that let y'all alter the internal sensor alerts. To see if yous can modify an alarm, check the sensor's settings for customizable options.

For more than information, run into the Knowledge Base: Which HTTP condition code leads to which HTTP sensor status?

For more information on error codes, see the Noesis Base: What does error lawmaking PExxx mean?

Here is an case of a sensor that is in the Down condition because of an internal sensor alert.

Probe Health Sensor with Disconnected Probe Alert

Probe Health Sensor with Disconnected Probe Alarm

Standard Limits for Channels

Some other type of alerts are alerts because of limits. These alerts are triggered when the measured value of a sensor is below or higher up a configured threshold limit. These limits change the sensor's status when they are breached. For case, you tin can set an SNMP CPU Load sensor to the Warning status whenever it measures values that you lot consider critical. This sensor then shows upwards in the alarms list.

This type of alert is only displayed when a value breaches the configured limits. If the value is normal over again in the next sensor browse, the sensor returns to the Up condition.

This limit only applies to the respective aqueduct.

Setting Limits for Sensor Channels

For more data on setting limits, see the video tutorial: How to set channel limits

With this configuration, the sensor changes to the Alarm condition (the approximate needle points to the yellowish area in the example below) if the channel values exceed the upper warning limit of lx percent and the Warning Limit Message is displayed in the sensor status. If the channel value exceeds the upper error limit of 80, the sensor turns to the Downward condition (the gauge needle points to the red expanse) and the Error Limit Message is displayed.

SNMP CPU Load in the Warning Status

Y'all tin use multi-edit if you want to utilize the same limits to sensors of the aforementioned type in a batch operation.

To see all sensors of this type, filter for the blazon: From the main bill of fare bar , select Sensors | By Type | SNMP CPU Load .
Mark the bank check boxes of the sensors that you want to edit.
Click in the card.
Open up the Channel Settings tab.
Select the channel that you desire to add a limit for. In this example, nosotros utilise the aqueduct Total, which is mutual to all selected sensors.
Then Enable alerting based on limits and enter the number in the correct field as described earlier.

When you lot are done, click OK to save these settings. The new limit is then applied to all selected channels from all selected sensors.

Multi-edit is only bachelor for channels that are common to all selected sensors.

Setting Channel Limits with Multi-Edit

Some sensors have predefined limits in the sensor settings, for example the SNMP Linux Disk Free sensor. Refer to the sensor's settings to arrange the limits (or behavior) for these sensors.

Absolute and Delta Values in Limits

The value that you need to configure in the limits depends on the type of data that the aqueduct delivers.

For channels that measure out absolute values (for CPU load and retentivity usage, for case), you accept to gear up limits with absolute values similar in the previous example.

You lot can also set limits for channels that measure delta (x.xx/sec) values. Let usa say you have an SNMP Traffic sensor and want to receive an alert when it reports errors. In this case, yous demand have into account that this is a delta measurement. In this example, yous could set the following limits for the aqueduct Errors in with a standard scanning interval (60 seconds).

Set the sensor to the Alert status when one error occurs
Set the sensor to the Down status when 30 errors occur

This example shows how to configure the limits for delta channels.

Setting Channel Limits with Delta Values

Because this aqueduct uses per second (delta) measurements, a single mistake that occurs over a standard sixty-second scanning interval is reported as 0.016 # per second. So the warning limit for ane unmarried RX error inside an interval is 0.1 (errors/sec). To get an alarm when there are 30 errors within a scanning interval, the limit needs to be 0.5 (errors/sec).

If no new errors occur in the adjacent scanning interval, the sensor turns back to the Upward status. To ensure that you do not miss whatever notifications for this sensor, set a notification trigger with 0 seconds. For more information, see Notification Triggers as Extensions to Alerts below.

Standard Lookups for Channels

PRTG also uses lookups for some sensors. In general, lookups make data more human friendly because they map condition values every bit returned by a device (usually integers) to more informative expressions in words that evidence you lot the status of a monitored device as a clear bulletin.

Additionally, lookups can also define the sensor status that is shown in correlation with sure condition codes, just like channel limits can define a sensor status, too. For example, PRTG can show a sensor in a gray Inactive status with channel values, provided by lookups, like Inactive instead of a numerical value like -1.

The diverse states displayed in gauges always follow the clockwise order Upwardly (green) < Warning (yellow) < Downward (red) < Unknown (gray).

SNMP HP LaserJet Hardware Gauge

Modifying a Standard Lookup: Instance

Yous can as well modify standard lookups to include new definitions. The post-obit code illustrates the lookup definition for the paper condition of the SNMP HP LaserJet Hardware sensor:

<?xml version="1.0" encoding="UTF-8"?>
<ValueLookup id="oid.paessler.hplaserjet.paperstatus" desiredValue="0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation=
"PaeValueLookup.xsd">
<Lookups>
<SingleInt land="Ok" value="0">
Paper Okay
</SingleInt>
<SingleInt state="Error" value="one">
Out of Paper or No Cassette Loaded
</SingleInt>
<SingleInt state="Error" value="2">
Manual Paper Feed Required
</SingleInt>
</Lookups>
</ValueLookup>

If y'all practise not want to receive alerts if the printer is out of paper, y'all have to:

Copy the file oid.paessler.hplaserjet.paperstatus.ovl to the \lookups\custom subfolder of the PRTG programme directory . Make sure that yous do non modify the file proper noun.
Open up this file with an editor.
Replace the first SingleInt state "Error" with "Ok".
Optionally supercede the message "Out of Paper or No Cassette Loaded" with "Ok".
Save the file.
Reload the lookups in the \lookups\custom subfolder.

The gauge at present displays the new state and the new message.

SNMP HP LaserJet Hardware Gauge Modified

SNMP HP LaserJet Hardware Judge Modified

For more than information on how lookups are divers, see section Ascertain Lookups.

Creating a New Lookup

It is also possible to create new lookups to use with whatsoever custom or standard sensor that supports lookups. If yous want to create a new lookup with the before example, you basically follow the same process except you save the lookup file in the \lookups\custom subfolder of the PRTG plan directory with a new name, for example oid.paessler.hplaserjet.mynewpaperstatus.ovl. Select the newly created lookup file in the sensor's channel settings.

Selecting a Newly Created Lookup

Custom Cord Lookups

Y'all tin besides ready upwards custom string lookups, which yous can only employ with the SNMP Custom String Lookup sensor. This is useful if you apply an object identifier (OID) that returns a known string value with possible states or values. To inform PRTG of the possible states or values, you lot accept to create a new lookup file that defines them.

For more information, meet the Noesis Base of operations: Monitor and "Lookup" a SNMP String value.

Notification Triggers every bit Extensions to Alerts

The status or the data of a sensor can trigger notifications. With this machinery, you tin configure custom external alerts. Which notification triggers are available depends on the kind of object you edit. You can define notification triggers that are activated past an 'on change' event. Some sensors offer the option to trigger a notification whenever sensor values accept changed.

Create Notification Triggers to Alert Y'all When a Value Changes

Before you fix up a change trigger, make certain that you enable the Trigger 'change' notification setting in the sensor'southward settings, otherwise the notification is never sent.

Trigger 'Change' Notification

Trigger 'Alter' Notification

Select the Notification Triggers tab to create a alter trigger for this sensor. Hover over and select Add together Change Trigger from the menu to add a new change trigger, or click next to a notification trigger to alter it. Every notification trigger initiates i or more than notifications.

Adding a Change Trigger

Click to salve the change trigger. Y'all are now notified when sensor values alter.

For more information on notification triggers, see department Notification Triggers Settings.

Create Notification Triggers to Match Your Limits/Lookups (State Based)

After you have set upwards alerts via limits or lookups, you can complement them with land-based notification triggers. On the Notification Triggers tab, hover over and select Add State Trigger from the card to add a new country trigger.

Adding a State Trigger

Click to save the the state trigger. You are now notified when the sensor states change.

If you want to receive alerts for more than one status, you have to add a state trigger for each condition.

A sensor's status tin change for other reasons such every bit internal sensor alerts. If you configure state-based notification triggers, yous are notified of these changes too.

More than

Noesis Base of operations