Get JSM alert details
jsm_get_alertRetrieve complete JSM alert details, including description, custom fields, responders, tags, and dedupe count, by ID or alias. Use after listing alerts to access the full payload.
Instructions
Retrieve the full detail of a single JSM alert, including its description, custom details/extraProperties, responders, tags and dedupe count.
Use this after jsm_list_alerts when you need the payload an integration attached to the alert (host, service, metric values, runbook links) — the list endpoint returns a thinner record without the description or details map.
Args:
identifier (string): the full alert id, or an alias when identifier_type='alias'
identifier_type ('id' | 'alias'): default 'id'
response_format ('markdown' | 'json'): default 'markdown'
Returns (json format): a single alert object with id, tinyId, message, description, status, acknowledged, snoozed, priority, source, owner, tags, responders, details (custom key/value map), extraProperties, count, createdAt, updatedAt, lastOccurredAt, and a report block with acknowledgedBy/closedBy. Responder ids are resolved to names where the credentials allow it.
Examples:
"What does alert #4821 actually say?" -> resolve the id via jsm_list_alerts, then call with identifier=
"Look up the alert our pipeline created with alias 'redis-latency-prod'" -> identifier="redis-latency-prod", identifier_type="alias"
Error handling:
HTTP 404 usually means a tinyId was passed instead of the full id. Resolve it with jsm_list_alerts first.
Aliases only resolve against OPEN alerts; a closed alert must be fetched by id.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| identifier | Yes | The alert's full id, or its alias if identifier_type='alias'. The short tinyId from the UI is NOT accepted by the API — search with jsm_list_alerts to resolve a tinyId to a full id. | |
| identifier_type | No | Which identifier was supplied. 'id' hits /v1/alerts/{id}; 'alias' hits the separate /v1/alerts/alias endpoint. | id |
| response_format | No | Output format. 'markdown' is compact and human-readable (default); 'json' returns every field for programmatic use. | markdown |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| alert | Yes |