HTTP Request

First you need to create a new Notification Template at Setup -> Account Settings -> Notification Templates. Here you choose Execute HTTP Action where you can specify your SIGNL4 webhook URL including the team secret, select the HTTP Method Post and enter the Payload including placeholders.

The payload might look like this: Title=Alert from PRTG&Site=%sitename&Message=%device %name %status %down (%message)

Here you can find a description about the supported placeholders: https://kb.paessler.com/en/topic/373-what-placeholders-can-i-use-with-prtg

So you have a format like this: Parameter1=Value1&Parameter2=Value2, etc.

Resolve Alerts: In order to support the resolution of alerts in SIGNL4 you can just add the following part to your SIGNL4 webhook URL:

?ExtIDParam=sensorid&ExtStatusParam=laststatus&ResolvedStatus=Up

So, the complete URL looks like this:

https://connect.signl4.com/webhook/team-secret?ExtIDParam=sensorid&ExtStatusParam=laststatus&ResolvedStatus=Up

Where “team-secret” is your SIGNL4 team secret. You then need to add the parameters “sensorid” and “laststatus” to the Payload:

Title=%device: %name&Message=%message&sensorid=PRTG: %sensorid&laststatus=%laststatus

You can find more information about the resolution of alerts in SIGNL4 here: https://www.signl4.com/blog/update-july-2020-resolve-alerts/. You can easily test the SIGNL4 notification template from here.

Then, at Sensors -> [Choose your sensor] -> Notification Triggers or at Devices -> Notification Triggers, you can specify your notification trigger including the conditions and the SIGNL4 notification template.

Alternative

You can also create separate HTTP actions for alerting and resolution (closing of an alert). This makes sense if you have multiple resolution statuses. In this case your data look like follows.

URL:

https://connect.signl4.com/webhook/team-secret

Replace team-secret with your team or integration secret.

Payload for the alert (Status Down):

Title=%device: %name&Message=%message&X-S4-ExternalID=PRTG: %sensorid&X-S4-Status=new

Payload for the resolution (Status Up, Closing of the alert):

Title=%device: %name&Message=%message&X-S4-ExternalID=PRTG: %sensorid&X-S4-Status=resolved

Two-way integration

For two-way communication there is a PRTG connector app available in SIGNL4 under Apps -> PRTG. This connector app adds two-way functionality to SIGNL4 alerting in PRTG. It allows you to acknowledge (or close or annotate) problems in PRTG directly from within your SIGNL4 app.

In order to use the Connector you need to make sure you have SIGNL4 alerting activated in PRTG. The configuration of the PRTG connector app is straightforward. You just need the PRTG username, password and the URL to your PRTG server. Please note that the URL needs to be reachable from the internet (e.g. port 443). The user account needs to have the according access rights for the PRTG API.

Email

Create a user within PRTG with the name of SIGNL4 and your team email address. Assign that user to a group that is monitoring existing sensors.

Note: In the screenshot below the user name is SIGNL4, email address is your team email and the user is part of the PRTG Users Group.

At this point the next time something triggers an alarm, your SIGNL4 team will be notified via the mobile app.

You can find more information about PRTG here.

See left how an alert looks in SIGNL4.

More information about the integration can be found be here.

Alert Optimization

SIGNL4 can further increase the visibility of alerts through its Signals and Services categories. Augmenting the color and icon of alerts will provide more relevant information at a glance without having to open the alert. You can also augment ticket alerts with maps or change the subject or message to a more comprehensible content.

Alert categories in SIGNL4 also allow to group ticket alerts and even to route those ticket notifications to your staff based on skills or other criteria. Screenshots show how to override text, colors and titles are triggered by keywords set within the mobile app.

Duty Scheduling