PRTG Integration

PRTG Network Monitor is Paessler's powerful network monitoring solution.

​What does Opsgenie offer to PRTG users?

Opsgenie provides a powerful bidirectional integration with PRTG. When a sensor is down in PRTG, a corresponding Opsgenie alert is automatically created, containing detailed information. Opsgenie provides rich notifications with on-call rotations, scheduling features, and alert escalations to ensure the best monitoring management for PRTG customers. As users execute actions on the alerts acknowledged, the sensor information on PRTG is automatically updated according to mapped actions preferred by the customer.

Functionality of the integration

PRTG to Opsgenie:

  • When "sensor status down" notification is sent form PRTG, it creates an alert in Opsgenie.
    • When "sensor status up" notification is sent from PRTG, the related alert is closed in Opsgenie.

Opsgenie to PRTG:

  • If Send Alert Updates Back to PRTG is enabled, actions for PRTG are executed in PRTG when the chosen action is executed in Opsgenie for alerts which are created by the PRTG.

  • This action mapping feature is explained in detail in the Action Mapping Feature section.

Add PRTG integration in Opsgenie

  1. Please create an Opsgenie account if you haven't done so already.
  2. Go to Opsgenie's PRTG Integration page.


An alternative for this step is to add the integration from the Team Dashboard of the team which will own the integration. To add an integration directly to a team, navigate to the Team Dashboard and open Integrations tab. Click Add Integration and select the integration that you would like to add.


For Free and Essentials plans, you can only add the integrations from the Team Dashboards, please use the alternative instructions given below to add this integration.

  1. Copy the integration URL to use in PRTG configuration.
  2. Click Save Integration.

Action Mapping Feature

  • Opsgenie allows customers to define action mappings between Opsgenie actions and PRTG actions.
  • To use the Action Mappings feature, provide the information listed below:

*Send Via OEC: Check to use on-premise PRTG

  • PRTG Username: API Username obtained from the account settings.
  • PRTG Passhash: API Passhash obtained from the account settings.
  • PRTG URL: The desired URL to use to visit your PRTG page.

For alerts created by PRTG

  • Use this section to map Opsgenie actions to a PRTG action when the source of the alert is PRTG (i.e When the alert is created by PRTG.)
  • Map different Opsgenie actions to different PRTG action. For example, to add "acknowledge a sensor" in PRTG, when the alert is acknowledged in Opsgenie. In order to do this, define If alert is acknowledged in Opsgenie, acknowledge sensor in PRTG mapping in Send Alert Updates Back to PRTG section.

Default Advance Filter Settings of PRTG integration in Opsgenie

Configuration on PRTG

  1. In PRTG, go to "Setup -> Account Settings -> Notification Templates". Click Add new notification.
  2. Select Execute HTTP Action.
  3. Paste the URL copied previously into the "URL" field.
  4. Select the Send SNI radio button and enter your instance's API URL in *Virtual Host (SNI).
  • US Region:
  • EU Region
  1. If you use PRTG version 16.x.24. and above paste the content of this text file, otherwise paste the content of this text file into "Postdata" field.
  2. Click Save.

Sample alert

Integration via OEC (for On Premise PRTG Usage)

Use Opsgenie's OEC and the PRTG script to update alerts on PRTG. This enables deployment of your own scripts/ability to modify the ones provided and execute customized actions on PRTG.

To use the PRTG integration package, follow the steps in the sections below through the end.

Download The Utility

For Red Hat Based Distributions


For rhel6 distributions, you can download this package.


If while installing the rpm package you get an error saying that the package is obsolated, you need to use "rpm -i opsgenie-prtg-1.0.4-rpm-x86-64.rpm --nodeps" instead.

If you get "is already installed" error, use "rpm -i opsgenie-prtg-1.0.4-rpm-x86-64.rpm --force" instead.

For Debian Based Distributions

For Windows

  • Download Opsgenie PRTG

  • Unzip opsgenie integration zip file which contains OEC package into a directory (C:\opsgenie\oec is the preferred path.) Follow the instructions here to install OEC on Windows.

  • In order to learn more about how to run OEC you can refer to the Running OEC documentation.

Configuring PRTG Integration for OEC

  • In order to use OEC utility, enable Send Via OEC.

  • Other configurations regarding PRTG can be done either via integration page or OEC configuration file config.json. The configuration via the integration page precedes the configuration file.

OEC Configuration

Use Opsgenie's OEC and the PRTG script to update alerts on PRTG.

To be able to execute actions in PRTG, OEC gets the configuration parameters from the configuration file. The configuration file can be found under /home/opsgenie/oec/conf/config.json


Copy the API key from the PRTG integration created above.


PRTG with subdomanin on it. Example


PRTG API Username under Account Settings at PRTG.


PRTG API Passhash under Account Settings at PRTG.

The package that you downloaded also includes OEC utility which is located under /usr/local/bin and the script that is needed to be run by OEC which is under /home/opsgenie/oec/scripts. After the configuration of OEC is done, you need to run it. In order to learn more about how to run OEC, you can refer to the Running OEC documentation.


  1. Former PRTG Integration users can convert the integration to make it work for bidirectional use by adding sensorId, {{sensorId}} key-value pair to Extra Properties field at your PRTG Integration configuration.

  2. If you are having trouble sending execute actions to OpsGenie, enable Send SNI and add for US, for EU.

Updated 4 months ago

PRTG Integration

PRTG Network Monitor is Paessler's powerful network monitoring solution.

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.