Jira Service Management

Open and close Jira Service Management alerts when Hyperping detects outages. Optionally route every alert to a specific JSM team so it lands with the right responders.

Hyperping creates a JSM alert when a monitor goes down and closes the same alert when it recovers.

Configure

On Atlassian

1. Create an API token at Atlassian Account Settings. Copy it — you will paste it into Hyperping in the next step.

2. Find your Cloud ID by opening your-site-name.atlassian.net/_edge/tenant_info in your browser, or follow Atlassian's guide. It looks like 18739352-b0c2-455a-bf44-b320ece12b08.

3. (Optional) Find the Team ID of the responder team you want alerts routed to. In JSM, go to Teams → select the team → Settings. The ID starts with og- followed by a UUID.

On Hyperping

Head to your Integrations page, then click Connect on the Jira Service Management card.

1. Cloud ID: the value you copied above.
2. Email: the Atlassian account that created the API token. Authentication uses email + token.
3. Atlassian site (optional): the subdomain from your URL (e.g. hyperping from hyperping.atlassian.net). Used to log full alert URLs for debugging.
4. API Token: the token from Atlassian Account Settings.
5. Responder team IDs (optional): one or more JSM team IDs, comma-separated. When set, every alert is created with these teams already assigned as responders, so JSM routes it without manual triage.

Click Test connection to confirm your Cloud ID, email, and API token are valid before saving.

Alert content

Each alert includes the monitor name, the received and expected status codes, the time and detected location, request timings (DNS, connection, TLS, first byte, download), and a link back to the Hyperping report.

Routing alerts to a team

JSM alerts without responders stay unowned and need manual assignment. The Responder team IDs field on the integration tells JSM which teams own the alert at creation time, which lets your on-call schedules and escalation rules fire immediately.

To route alerts to several teams at once, paste multiple IDs separated by commas:

og-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx, og-yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy

To stop routing, clear the field and save. New alerts will be created without responders.

Test the integration

Create a monitor that returns an error, such as a URL that responds with 404. The next failed check fires the alert and you should see it appear in JSM, already assigned to the responder team if you set one.

Troubleshooting

Alerts are created but no team is assigned. Check that the team ID starts with og- and matches what you see in Teams → Settings in JSM. A typo or trailing space silently drops the field on the JSM side.

Authentication failed. The email must be the Atlassian account that owns the API token, not a project member. Regenerate the token if you are unsure.

Cloud ID not found. Open your-site-name.atlassian.net/_edge/tenant_info in the browser where you are logged in to Atlassian and copy the cloudId value verbatim.