Linode Instances
Linode Statistics View
https://api.linode.com/v4/linode/instances/{linodeId}/statsReturns CPU, IO, IPv4, and IPv6 statistics for your Linode for the past 24 hours.
Path Parameters
ID of the Linode to look up.
Request Samples
- Shell
curl -H "Authorization: Bearer $TOKEN" \
https://api.linode.com/v4/linode/instances/123/stats
Response Samples
- 200
- default
{
"cpu": [],
"io": {
"io": "",
"swap": ""
},
"netv4": {
"in": "",
"out": "",
"private_in": "",
"private_out": ""
},
"netv6": {
"in": "",
"out": "",
"private_in": "",
"private_out": ""
},
"title": "linode.com - my-linode (linode123456) - day (5 min avg)"
}Responses
200: The Linode's stats for the past 24 hours.
Percentage of CPU used.
Input/Output statistics.
Block/s written.
Block/s written.
IPv4 statistics.
Input stats for IPv4, measured in bits/s (bits/second).
Output stats for IPv4, measured in bits/s (bits/second).
Private IPv4 input statistics, measured in bits/s (bits/second).
Private IPv4 output statistics, measured in bits/s (bits/second).
IPv6 statistics.
Input stats for IPv6, measured in bits/s (bits/second).
Output stats for IPv6, measured in bits/s (bits/second).
Private IPv6 input statistics, measured in bits/s (bits/second).
Private IPv6 output statistics, measured in bits/s (bits/second).
The title for this data set.
default: Error
What happened to cause this error. In most cases, this can be fixed immediately by changing the data you sent in the request, but in some cases you will be instructed to open a Support Ticket or perform some other action before you can complete the request successfully.
The field in the request that caused this error. This may be a path, separated by periods in the case of nested fields. In some cases this may come back as "null" if the error is not specific to any single element of the request.