get_alerts
Retrieve open or cleared LogicMonitor alerts filtered by severity, device, group, datasource, or time range to focus incident triage and review.
Instructions
Get open or cleared alerts from LogicMonitor, optionally filtered by severity (critical, error, warning), device, group, datasource or time
For Kubernetes clusters, use group_id (from get_device_groups) instead of device; the device name filter does not work reliably for K8s resources.
Common mistakes: startEpoch/endEpoch use SECONDS not milliseconds. String filter values need double quotes (e.g., monitorObjectName:"hostname").
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": "get_alerts"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| acked | No | Filter by acknowledged status | |
| limit | No | Max results (max 1000) | |
| sdted | No | Filter by SDT status | |
| device | No | Filter by device name (substring match) | |
| filter | No | Raw filter expression (overrides other filters). Example: severity:4,cleared:false | |
| offset | No | Pagination offset | |
| status | No | Filter by status | |
| cleared | No | Filter by cleared status | |
| group_id | No | Filter by device group ID (matches all devices) | |
| instance | No | Filter by instance name (substring match) | |
| severity | No | Filter by severity | |
| datapoint | No | Filter by datapoint name (substring match) | |
| device_id | No | Read this device's own alert list; every other filter applies there except group_id, which is refused beside it | |
| end_epoch | No | Filter alerts started before this epoch timestamp | |
| datasource | No | Filter by datasource/template name (substring match) | |
| start_epoch | No | Filter alerts started after this epoch timestamp |