Integrate PRTG with StatusHub
This article takes you through the steps to integrate your PRTG account with StatusHub.
In StatusHub:
To connect PRTG into your account, click on 'Services and Integrations' in the Hub Config section.
In the Services and Integrations section, click the right arrow.
You will then see these options appear. Click on the 3 dots to the right to reveal the drop-down menu and choose the Edit option.
Under Edit services, select Integrations and choose PRTG, then save.
After you select the PRTG option, we will generate a webhook for you to use at the PRTG application.
IN PRTG:
1. Add notification template:
Move to Account Settings and create your Notification Template.
Add the name of the template and choose ‘Always notify immediately, never summarize’ option in the ‘Notification Summarization’ section.
Scroll down to the ‘Execute HTTP Action’ section and enable it. In the URL field paste the webhook URL copied previously from StatusHub. Choose the POST method and fill the payload.
Example payload:
datetime=%datetime&laststatus=%laststatus&status=%status&timezone=%timezone&group=%group&device=%device
PRTG fields mapping in StatusHub
| PRTG field | StatusHub meaning |
|
%group + %device + %status (required if shtitle is not provided) |
Used to construct Incident title in form: {{%group}} {{%device}}: {{%status}} |
| %timezone (required) | Time zone used to calculate Incident Update start time value. |
| %datetime (required) | Start time of Incident Update. |
| %laststatus (required) |
Service status (PRTG -> StatusHub):
|
| %message (required) | Incident Update message. |
Other PRTG fields are currently ignored by StatusHub.
In addition to PRTG fields there are additional fields that can be used to enrich data sent to StatusHub:
| Field name | StatusHub meaning |
| shtitle |
Incident title. If provided, will be used instead of combination of %group, %device and %status |
| sheventid |
Unique identifier of Incident. Can be used to support multiple incidents for the same service. If not provided, StatusHub will assume that all updates should be added to existing open Incident created from PRTG on that service. If such an incident does not exist, a new one will be created. |
| shdraft | Should the Incident update be in draft mode. |
| shsilent |
Should the Incident update be a silent update. Silent updates do not trigger notifications to subscribers. |
Example of Payload with additional StatusHub fields:
datetime=%datetime&laststatus=%laststatus&status=%status&timezone=%timezone&shtitle=My%20incident%20title&sheventid=da5d6d8941b3&shdraft=false&shsilent=true
Once filled click ‘Create’ button
2. Add Notification Trigger:
In your sensor, configure Notification Trigger. Example:
In available fields add appropriate state and previously configured template.
Note:
- Supported states are: Warning, Down and Up.