Open an incident by hand
open_incidentOpens an incident for what the checks cannot see: a slow service, a problem a customer reported. With a message it publishes the first update on the status pages that show its monitors (and emails their subscribers on Pro plans); alert pages the monitors' contacts once. It stays open until resolve_incident and never counts as downtime. Every plan, at most 20 open. Free.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"title": "<title>"
},
"name": "open_incident"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| alert | No | Alert the monitors' contacts once, and again when it is resolved. Ask the user first. | |
| state | No | The first update's state, investigating by default. | |
| title | Yes | What the dashboard, alerts and status pages call it. | |
| message | No | Optional first update for the visitors of the status pages that show the monitors. | |
| severity | No | How serious the problem is. | critical |
| monitor_ids | No | The monitors it affects (GET /monitors): its updates show on the published status pages that show any of them. None or up to 50. |