Issue Summary

PRTG integration is failing to create alerts in Opsgenie component of Jira Service Management (JSM). 

PRTG uses the SNI url api.opsgenie.com and sends data to Opsgenie via HTTP POST method.
The post requests are failing in PRTG due to unsupported HTTP 1.0.

The PRTG logs say :
Stat disconnected
HTTP/1.1 426 upgrade required.

Screenshot attached.

Steps to Reproduce

1. Create a PRTG Integration to Opsgenie
2. Create a PRTG Alert. The alert is not passed to Opsgenie and the HTTP post fails.

Expected Results

The alert in PRTG should create a related alert in Opsgenie.

Actual Results

No alert gets created in Opsgenie from PRTG.

Workaround

We have put together a PowerShell script so that the integration uses Powershell instead of PRTG as the REST client, which will remove the dependency on PRTG's rest client.

What are the dependencies and what OS is supported?

• Windows Server with Powershell 3 or above.
• Since it is not possible to set Powershell’s -executionpolicy bypass parameter, the user needs to ensure that the execution policy is set to remotesigned or allsigned.
• This script has only been tested with the latest version of PRTG, previous versions might not be supported. How to install the script?

  How to Install the Script

1. Download and extract the PRTG_Workaround.zipand obtain the Opsgenie.ps1 and Powershell_parameters files.
2. Copy to this location “C:\Program Files (x86)\PRTG Network Monitor\Notifications\EXE”
3. Open PRTG, go to “Setup” >> “Account Settings“ >> “Notification Templates”
4. Click the blue plus sign located to the right of the “Notification Templates” table, then click “Add Notification Template”
5. Give the template a name “OpsgenieScript“ and make sure its status is “Started“

6. Toggle on the option “Execute Program“, from the “Program file“ drop-down list select “Opsgenie.ps1“. Open the file Powershell_parameters that you downloaded from this page, copy all its content and paste it into the “Parameters“ field, replace [API URL] with the API URL contained in your PRTG integration settings in the Opsgenie UI.
In “Domain or Computer name“ you will need to specify Windows Domain name (if the PRTG server is an Active Directory is domain member) or Computer name (if a non Active Directory computer)
Next, specify a username and password credentials for running the script, please do not use an Administrator user, please create service account user if possible.

 

7. Lastly, we need to configure triggers. In PRTG select “Devices“ then click “Notification Triggers“, ** Click the blue plus sign located to the right of the “Notification Triggers” table, then click “Add State trigger” configure the following settings:When sensor state is Down for at least 60 seconds, perform  OpsgenieScript*When sensor state is *Down for at least 300 seconds, perform  OpsgenieScript and repeat every 5 minutesWhen sensor leaves Down state after a notification was triggered, perform  OpsgenieScript*Create a second state trigger that handles warnings.When sensor state is *Warning for at least 60 seconds, perform  OpsgenieScript*When sensor state is *Warning  for at least 300 seconds, perform  OpsgenieScript and repeat every 5 minutesWhen sensor leaves Warning state after a notification was triggered, perform  OpsgenieScript|