List JSM alert activity logs
jsm_list_alert_logsList a JSM alert's system activity log to trace state changes, notifications, escalations, and automated actions. Use it to find why nobody was paged or when an alert was escalated and to whom.
Instructions
List the system activity log for a JSM alert — every state transition, notification, escalation and automated action, newest first by default.
Use this to answer "why did nobody get paged?" or "when was this escalated and to whom?". Logs are system-generated; human comments live in jsm_list_alert_notes instead.
Args:
alert_id (string): the full alert id (not the tinyId)
limit (number): 1-100, default 20
order ('asc' | 'desc'): default 'desc'
offset (string, optional): opaque cursor from a previous response's next_cursor
response_format ('markdown' | 'json'): default 'markdown'
Returns (json format): { "logs": [{ "log": string, "owner": string, "createdAt": string, "type": string, "offset": string }], "pagination": { "count": number, "has_more": boolean, "next_cursor": string } }
Examples:
"Trace the escalation path for this alert" -> alert_id=, order="asc", limit=100
"Who acked this and when?" -> alert_id=, limit=20
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of records to return (1-100, default 20). | |
| order | No | Chronological order of returned entries (default 'desc', newest first). | desc |
| offset | No | Cursor from a previous response's 'next_cursor'. These endpoints use opaque cursors, not numeric offsets. | |
| alert_id | Yes | Full alert id, e.g. '9b251e07-73c9-4907-9996-8cb53a6a20d0-1704440650350'. This is NOT the short tinyId shown in the JSM UI — get the full id from jsm_list_alerts first. | |
| 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 |
|---|---|---|---|
| logs | Yes | ||
| pagination | Yes |