View Linode metrics
To view metrics for your Linode:
- Log in to the Cloud Manager and click the Linodes link in the sidebar.
- Select your Linode. The Linode's details page appears.
- Click the Metrics tab.
- For legacy solution, review the graphs representing the legacy metrics. Use the dropdown menu to adjust the time period.
- For Akamai Cloud Pulse solution, click the Try the Metrics (New) button to see the Akamai Cloud Pulse metrics. You can adjust the time range, apply filters and other controls on how the data is displayed. For more information on using Akamai Cloud Pulse dashboards, see Metrics dashboards.
You can switch back to the legacy view at any time. Click Switch to legacy Metrics.
Akamai Cloud Pulse vs. legacy metricsAs you compare the experience between legacy and Akamai Cloud Pulse metrics, you may notice differences in how some metrics are collected and reported. See the Transition to the new Metrics and Alerts guide for detailed comparison.
Akamai Cloud Pulse metrics for Linodes (Beta)
Linodes metrics are automatically collected and stored by Akamai Cloud Pulse. Metrics provide time-series data that reflects usage, performance, and operational behavior over time.
You can view and analyze metrics data in dashboards in Cloud Manager. Metrics can also be retrieved programmatically through the Linode API, exported to external tools, and used to define conditions for alerts.
Feature availabilityMetrics and alerts for Linodes are currently in beta and are rolling out gradually. If they are not visible in your account, access may not be available in your region yet.
Data retention periodAkamai stores 93 days of historical metrics data for Linodes. If you would like to use data outside of the 93 day window, you must export your metrics data to another storage location. For more information, see Export metrics to external tools.
Supported metrics
This table describes the metrics available for Linodes, including API equivalents and units.
| Metric | API equivalent | Description | Units | Reporting Frequency |
|---|---|---|---|---|
| CPU Usage By Instance | avg_vm_cpu_usage_pct | Total CPU utilization across all CPU cores, normalized as a percentage of allocated capacity (1-100%). Note: CPU usage is now normalized across all CPU cores (0-100%) which differs from legacy CPU usage reporting. For example, 4 CPU cores at 50% usage reports 50% CPU usage. | % | 5 minutes |
| Local disk I/O By Instance | vm_disk_io_rate_iops | Number of input and output operations performed on the Linode's local disk storage per second, which can be used to understand how well the disk can handle concurrent read and write requests | IOPS | 5 minutes |
| Network Traffic In By Instance | avg_vm_network_traffic_rate_kbps | Amount of incoming data received by the Linode across its network interfaces measured as throughput in kilobits per second (kbps), and used to understand overall network utilization | kbps | 5 minutes |
| Network Traffic Out By Instance | avg_vm_network_traffic_rate_kbps | Amount of outgoing data sent by the Linode across its network interfaces, measured as throughput in kilobits per second (kbps), which can be used to manage billing, plan capacity, and identify data-intensive applications | kbps | 5 minutes |
Supported dimensions
This table describes the dimensions available for Linodes. Dimensions are descriptive attributes used to categorize and filter metrics data, enabling more detailed analysis.
| Dimension | API equivalent | Description |
|---|---|---|
| Disk type | type | Type of local disk device, disk or swap, indicating whether it's used for persistent storage or configured as a swap space that extends the system's RAM |
| Disk operation | operation | Indicator of whether disk activity is read or write, which enables you to analyze performance differences between data retrieval and data storage operations |
| Disk device | disk_device | The specific local disk on which I/O operations are being performed, for example, /sda, /sdb, and /sdc |
| Protocol | protocol | Indicator of the IP version used for the network traffic. Either ipv4 or ipv6. |
| Traffic pattern | pattern | Indicator of whether network traffic is public or private and inbound or outbound: publicin, publicout, privatein, privateout. |
Export metrics to external tools
Use the Akamai Distribution of the OpenTelemetry Collector for Akamai Cloud Pulse (the collector) to export NodeBalancers metrics to supported observability platforms for visualization and analysis.
For an overview of the collector, see Export metrics to external tools. For detailed descriptions of configurable parameters, see Receiver configuration.
Updated 3 days ago