...
| Expand | ||
|---|---|---|
| ||
Either share the OP5 file to the remote OP5 monitor or copy the link on the opening page.
Before rpm upgrades, back up your configuration files. During upgrades, the rpm package does not overwrite the existing configuration. It saves the new default configuration file as integration.conf.rpmnew. To update from version 201X-XX-XX to 2.X.X, add the |
Add OP5 integration
| Info |
|---|
You can add this integration from your team dashboard If you're using Opsgenie's using the Free or Essentials plan, or if you’re using Opsgenie with Jira Service Management's Standard plan, you can only add this integration from your team dashboard as the Integrations page under Settings is not available in your Standard plan in Jira Service Management. To access the feature through Adding the an integration from your team dashboard will make team’s operations page makes your team the owner of the integration. This means Opsgenie will assign Jira Service Management only assigns the alerts received through this integration to your team only. To do that, |
Go to your team’s
...
Select Integrations, and select Add integration.
Follow the rest of the steps to complete the integration.
Go to your team’s operations page.
On the left navigation panel, select Integrations and then Add integration.
Run a search and select “OP5”.
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 API key.
You will use this key while configuring the integration in OP5 later.Select Turn on integration.
The rules you create for the integration will work only if you turn on the integration.
...
If everything goes well, alerts are created in Jira Service Management for every notification created in OP5.
Map alert actions
You can define mappings between Jira Service Management actions and OP5 actions (also when the source of the alert is OP5), which requires additional authentication for your OP5 account.
Username: The username of your OP5 account
Password: The password of your OP5 account
OP5 Monitor URL: This is the domain name of your OP5 Monitor. For example: https://19.167.1.143
For alerts created by OP5
In the Send alert updates back to OP5 section, map Jira Service Management actions to OP5 actions when the source of the alert is OP5 (when the alert is created by OP5 integration itself). Map different Jira Service Management actions to different OP5 actions. For example, acknowledge the alert in OP5, when the alert is acknowledged from OP5. To do this, define If alert is acknowledged in Jira Service Management, acknowledge in OP5 mapping in Send alert updates back to OP5 section.
Configure Jira Service Management to update OP5
...
If unsure of the problem, set the JEC's script log level to debug, try again, and contact us and share the log files found under /var/log/jsm/.
Map alert actions
You can define mappings between Jira Service Management actions and OP5 actions (also when the source of the alert is OP5), which requires additional authentication for your OP5 account.
Username: The username of your OP5 account
Password: The password of your OP5 account
OP5 Monitor URL: This is the domain name of your OP5 Monitor. For example: https://19.167.1.143
For alerts created by OP5
In the Send alert updates back to OP5 section, map Jira Service Management actions to OP5 actions when the source of the alert is OP5 (when the alert is created by OP5 integration itself). Map different Jira Service Management actions to different OP5 actions. For example, acknowledge the alert in OP5, when the alert is acknowledged from OP5. To do this, define If alert is acknowledged in Jira Service Management, acknowledge in OP5 mapping in Send alert updates back to OP5 section.
...