Atlassian JSM
Open an alert for emergency notifications (formerly Opsgenie).
What it does
Opens an Atlassian Jira Service Management Operations (JSM Ops) alert for each notification that reaches it. This allows Prowl to page your on-call. This service was formerly Opsgenie.
Before you start
Get an API key from JSM:
- Navigate to "Operations"
- Choose "Teams" from the page tabs
- Choose the team for Prowl to use
- Choose "Integrations" from the page tabs
- Choose "Add Integration" then "API"
- Pick an Integration name such as "Prowl"
- Choose "Turn on integration"
- Copy the "API key"
Set it up
Paste the key into "API key". Prowl checks if it's correct immediately, without opening an alert.
Only Emergency notifications open alerts by default. You can lower the minimum priority on the Destination if you want more.
Check it works
Before you send a notification, make sure whoever will get paged expects it. Send an Emergency priority notification, and an alert will be opened.
Options and behavior
Each notification opens one alert. Every alert is tagged prowl.
Priorities carry over. Emergency opens a P1, High a P2, Normal a P3, Moderate a P4, and Very Low a P5.
If Prowl retries sending a notification after receiving a transient error, it will not open a second alert by accident.
Prowl does not acknowledge or close alerts. For example, a Heartbeat recovery notification is independent. (Want auto-close behavior? Contact us so we get a feel for demand.)
Troubleshooting
The Destination needs attention
If the key stops working because it's revoked or the integration is deleted, Prowl marks the Destination "Needs attention". You can choose "Reconfigure" to update to a new key.
Alerts don't appear
Check that Status reads "On" on the integration's page. New integrations are created Off. Don't confuse it with the separate "Notifications" toggle, which is already On.
Disconnect or replace it
Remove the Destination to stop opening new alerts. Alerts already opened will not be closed.