...
Jira Service Management to PRTG
If Send Alert Updates Back alert updates back to PRTG is enabled, actions for PRTG are run in PRTG when the chosen action is run in Jira Service Management for alerts which that are created by the PRTG.
The mapping feature is explained in detail in the Action Mapping section https://operations-help.atlassian.net/wiki/spaces/OPSHELP/pages/4292784/Integrate+with+PRTG#Map-alert-actions.
Set up the integration
PRTG is a bidirectional integration. Setting it up involves the following steps:
...
Go to your team’s operations page.
On the left navigation panel, select Integrations and then Add integration.
Run a search and select “PRTG”.
On the next screen, enter aname for the integration.
Optional: Select a team in Assignee team if you want a specific team to receive alerts from the integration.
Select Continue.
The integration is saved at this point.Expand the Steps to configure the integration section and copy the integration URL.
You will use this URL while configuring the integration in PRTG later.Select Turn on integration.
The rules you create for the integration will work only if you turn on the integration.
Map alert actions
You can define action mappings between Jira Service Management actions and PRTG actions (also when the source of the alert is PRTG), which requires additional authentication for your PRTG account.
Select Edit on the configuration page to edit the integration.
Under the Authenticate for sending alert updates to PRTG section, select Authenticate with a PRTG account check box.
Enter values for the following:
Username: The email address you use to log in to from your PRTG account settings
Passhash: The passhash you use to log in to from your PRTG account settings
PRTG URL: The URL of your PRTG login page.
Select Save.
Expand the Outgoing section.
Select Send alert updates back to PRTG check box.
Select alert actions for which you want to send updates back to PRTG.
Every time an action you selected happens, a corresponding sensor is acknowledged in PRTG.
Configure the integration in PRTG
Jira Edge Connector is a prerequisite for configuring the outgoing authentication of PRTG integration. Download the latest version of the PRTG package from this repository.
In PRTG, go to Setup > Account Settings > Notification Templates.
Select Add new notification > Execute HTTP Action.
Paste the URL you copied while adding the integration in Jira Service Management into URL.
Select Send SNI and enter the URL from Step 3 into the domain and subdomain fields of Virtual Host (SNI). US Region:
api.jsm.comEU Region
api.eu.jsm.comCopy the POST data (from the file linked to, as applicable) and paste it into Postdata.
For PRTG version 16.x.24. and above, use this filepost data.
For other versions, use this filepost data.
Select Save.
...
Authenticate via JEC (for on-premise PRTG)
Use Jira Edge Connector (abbreviated as JEC) is a prerequisite for configuring the outgoing authentication of PRTG integration. You can combinedly use JEC and the PRTG script scripts to update alerts on PRTG. This enables deployment of your own scripts/ability to With this setup, you can deploy your own script, modify the ones provided and execute , or run customized actions on PRTG.
...
To use STEP 1. Download and install the PRTG integration package, follow the steps in the following sections:
...
Download the latest version of JEC
...
package from this repository.
...
Install the PRTG package
For
| Expand | |||
|---|---|---|---|
| |||
Run the following command :
| |||
If while installing the rpm package you get an error saying you figure that the rpm 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. |
...
obsolete, run the following command instead:
If you figure that the rpm package is already installed, run the following command instead:
|
| Expand | ||
|---|---|---|
| ||
Run the following command:
|
...
|
...
| Expand | ||
|---|---|---|
| ||
|
...
|
...
|
...
To learn more about how to run JEC, refer to the Running JEC documentation.
Configure the integration PRTG Integration for JEC
...
To use the JEC utility, select Send Via JEC.
...
Learn more about running JEC |
...
STEP 2: Configure the PRTG integration for JEC
In Jira Service Management, go to the integration configuration page.
Expand the Outgoing section.
Select the Authenticate with Jira Edge Connector only check box.
You can make the other configuration through the integration configuration page or the JEC configuration file, config.json. The configuration
...
set through the integration
...
configuration page takes precedence over what’s in config.json.
...
STEP 3: Configure JEC
Use JEC and the PRTG script to update alerts on PRTG. To run actions in PRTG, JEC gets the configuration parameters from the configuration file. The configuration file can be found under , config.json (found at /home/opsgeniejsm/oecjec/conf/config.json).
Configuration parameters
apiKey – Copy the The API key from you copied while adding the PRTG integration created above.integration in Jira Service Management
prtgUrl – The PRTG URL with a subdomain on in it. Example: https https://opsgeniejsm.my-prtg.com
username – The PRTG API Username username under Account Settings at in PRTG.
passhash – The PRTG API Passhash passhash under Account Settings at in PRTG.
The downloaded package that you downloaded also includes the JEC utility which is located under (found in /usr/local/bin) and the script that is needed JEC needs to be run by JEC which is under run (found in /home/opsgeniejsm/oecjec/scripts. After the configuration of JEC is done, you need to run it. To learn more about how to run JEC, you can refer to the Running JEC documentation.
Troubleshooting
...
). Be sure to run JEC after configuring it.
Learn more about running JEC documentation.
...
Troubleshoot issues
If you have an older setup of the integration and want to make it work bidirectionally, add
sensorId, {{sensorId}}key-value pair to
...
alert properties in your PRTG Integration configuration.
If you are having trouble sending execute actions to Jira Service Management, enable Send SNI
...
.
...