Create application alert
create_application_alertMake an alert on one environment of an Application, on its own measurements: failed requests (failed_share_pct), p95 response time (p95_ms) or restarts. It fires when the reading stays above the threshold for hold_minutes and sends to the places in send_to. The organisation needs a place to send alerts to first (list_alert_destinations), and an application has at most 50 alerts. Needs alerts.manage, or applications.write on the application. In the confirmation, name the application, the environment, the condition and where it sends to.
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>",
"environment_id": "<environment_id>",
"name": "<name>",
"condition": "<condition>",
"send_to": "<send_to>"
},
"name": "create_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. | |
| 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). |