Monitoring hosts
monitoring_hostsThe ready-made question: availability and load of a project's servers over the last day or week, from its monitoring (get_monitoring) — per host its availability (% of scrapes answered), load per core, CPU busy %, memory used %, root disk used % (average, worst and now) and the processes the kernel killed for memory. Answers the PromQL it ran ('queries') and 'source': the Grafana, the data source, when it was asked and the period counted. Ask this before writing PromQL of your own. For the people who work in the project and the company; at most 60 reads of a project's monitoring an hour, agents and people together. A refusal has a 'state': not_connected (with the 'url' of the screen that connects one), off, refused, sealed, unreachable, busy, too_big, missing, no_access, not_found, bad_request.
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": {
"project": "<project>"
},
"name": "monitoring_hosts"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| period | No | 'day' (default) or 'week'. | |
| project | Yes | Project key, e.g. 'PM'. |