Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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:

...

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.

...

Authenticate via JEC (for on-premise PRTG)

Jira Edge Connector (abbreviated as JEC) is a prerequisite for configuring the outgoing authentication of PRTG integration. You can combinedly use JEC and PRTG scripts to update alerts on PRTG. With this setup, you can deploy your own script, modify the ones provided, or run customized actions on PRTG.

...

  • 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.

...

See also

Explore integration types

Explore integration actions

Add integration rules