analyze_alerts
Analyze an alert window to see how many alerts fired, when, which belong together, how noisy alerting is, which datasources burst, and which portal changes preceded a spike.
Instructions
Analyze one alert window: call this for how many alerts fired and when, which alerts belong together, how noisy alerting is, which datasources burst, or which portal changes preceded a spike over the last hours. One read of the window's active and cleared alerts, under the severity, device, group and datasource filters, feeds every section; 'statistics' gives active and cleared totals, counts by severity, the ten busiest devices and datasources, and the volume of each hour, cleared alerts included; 'clusters' groups two or more alerts by device, by datasource and by signature (datasource and datapoint) and lists the five largest of each type, each with its alert count, its ten most severe alert ids, up to ten of its devices with device_count, and first and last start times, while cluster_count and by_type count every cluster; a device cluster names the device_id its alerts share, null for a website or two devices under one name; 'noise' gives a 0 to 100 score from the entropy of alerts over datasource and datapoint (weight 40), flaps, an alert on the same device and datapoint that re-fires within 30 minutes of clearing (30), and repeats, a combination with three or more alerts (30), with the first ten flap pairs and tuning recommendations; 'bursts' gives the windows of window_seconds on one datasource that hold at least min_alerts alerts on min_devices devices, the ten largest listed and all counted in bursts_detected; 'changes' reads the audit log once and pairs each change (a create, update, delete or import, read from the entry's description) with the first 5-minute alert spike, a bucket above the mean by one standard deviation, within correlation_window_minutes after it, with a confidence from 1.0 to 0.5; it lists the ten pairs of highest confidence and counts them all in total_correlated. Narrow the filters to see what a bounded list leaves out. truncated says when the 5000-alert cap cut either read short. Use get_alerts to list or page through the alerts themselves.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "analyze_alerts"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| hours | No | Hours the window reaches back from now (default: 24) | |
| device | No | Only alerts on devices whose name contains this | |
| analyses | No | Sections to compute (all if omitted) | |
| group_id | No | Only alerts on devices in this device group | |
| severity | No | Only alerts of this severity | |
| datasource | No | Only alerts from datasources whose name contains this, regardless of case | |
| min_alerts | No | Fewest alerts a burst holds (default: 10) | |
| min_devices | No | Fewest distinct devices a burst holds (default: 3) | |
| window_seconds | No | Burst window length in seconds (default: 60) | |
| correlation_window_minutes | No | Longest gap from a change to the spike it pairs with (default: 30) |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| hours | Yes | Hours the alert window reaches back. | |
| noise | No | ||
| bursts | No | ||
| portal | No | The portal the call ran against, in multi-portal mode. | |
| changes | No | ||
| analyses | Yes | ||
| clusters | No | ||
| api_total | Yes | ||
| truncated | Yes | ||
| statistics | No | ||
| total_alerts | Yes |