Update application alert
update_application_alertChange one of an Application's own alerts (own=true in list_application_alerts): its name, environment, condition and the places it sends to are replaced by what this call sends, so send every one of them, reading the current values with list_application_alerts first; severity is kept when left out. What the evaluator recorded on the alert is kept. An organisation rule listed beside the application's alerts is refused: change it with the organisation alert tools. Needs alerts.manage, or applications.write on the application.
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": {
"application_id": "<application_id>",
"alert_id": "<alert_id>",
"environment_id": "<environment_id>",
"name": "<name>",
"condition": "<condition>",
"send_to": "<send_to>"
},
"name": "update_application_alert"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | The alert's name, 1 to 100 characters, for example 'Failed requests'. In the organisation's alert list it reads '<application> · <environment> · <name>'. | |
| send_to | Yes | The ids of 1 to 5 places the alert sends to, as list_alert_destinations returns them, each named once. | |
| alert_id | Yes | The alert's id (alert_id), as list_application_alerts returns it. Only an alert with own=true is the application's to change or remove. | |
| severity | No | The alert's severity. On a create it defaults to warning; on an update leaving it out keeps the alert's severity. | |
| condition | Yes | When the alert fires: the reading of metric stays above threshold for hold_minutes. | |
| application_id | Yes | The Application's id. | |
| environment_id | Yes | The id of the environment the alert watches: one of the application's environments (get_application_configuration lists them). |