Get CPU, memory and network use of a deployment
edgegap_get_deployment_metricsSummarize a deployment's CPU, memory, and network use over time with anomaly flags to size a version or diagnose whether a crash was memory or CPU starvation before redeploying.
Instructions
Summarise a deployment's resource use over time: CPU, CPU throttling, memory and network, each as latest, average, p95 and peak, with the API's own labels, plus anomaly flags (spikes above mean + 3 sd, a rising trend such as a memory leak, any CPU throttling) collected in anomalies. Use it to size a version (cpu_units, memory_mb) from a real match, or to check whether a crash was memory or CPU starvation before redeploying. Defaults to the whole life of the deployment. To compare two versions, use edgegap_compare_versions.
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": {
"request_id": "<request_id>"
},
"name": "edgegap_get_deployment_metrics"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| step | No | Averaging step, e.g. "30s" or "5m". Default: the API's. | |
| end_time | No | ISO 8601. Default: now, or when it stopped. | |
| request_id | Yes | The request_id of the deployment. | |
| start_time | No | ISO 8601. Default: when the deployment started. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cpu | No | ||
| note | No | ||
| memory | No | ||
| totals | No | ||
| request_id | No | ||
| network_receive | No | ||
| network_transmit | No | ||
| cpu_throttle_rate | No |