NodeBalancers metrics
NodeBalancers 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.
Limited availabilityAkamai Cloud Pulse metrics for NodeBalancers are currently in limited availability and may not be accessible from your account. To gain access, please open a support ticket and request to join the limited availability program for this feature.
Data retention periodAkamai stores 93 days of historical metrics data for NodeBalancers. 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 NodeBalancers, including API equivalents and units.
For API operations, use service_type set to nodebalancer. All NodeBalancer metrics use the gauge metric type, which means their values can increase or decrease over time.
| Metric | API equivalent (metric) | Description | Units |
|---|---|---|---|
| Ingress traffic rate | nb_ingress_traffic_rate | Total traffic into and out of the NodeBalancer on its inbound (front-end) side. This includes incoming connections from the internet or external clients | B/s |
| Egress traffic rate | nb_egress_traffic_rate | Total traffic into and out of the NodeBalancer on its outbound (back-end) side. This includes traffic sent to and received from backend nodes | B/s |
| Ingress TCP traffic rate | nb_ingress_tcp_traffic_rate | TCP traffic received on the NodeBalancer’s inbound ports from external clients, measured in bytes per second | B/s |
| Egress TCP traffic rate | nb_egress_tcp_traffic_rate | TCP traffic sent from the NodeBalancer to the backend nodes, measured in bytes per second at the backend ports | B/s |
| Ingress UDP traffic rate | nb_ingress_udp_traffic_rate | UDP traffic received on the NodeBalancer’s inbound ports from external clients, measured in bytes per second | B/s |
| Egress UDP traffic rate | nb_egress_udp_traffic_rate | UDP traffic sent from the NodeBalancer to the backend nodes, measured in bytes per second at the backend ports | B/s |
| Total active sessions | nb_total_active_sessions | Number of active client-to-backend sessions managed by the NodeBalancer | count |
| Active TCP sessions | nb_active_tcp_sessions | Number of TCP active client-to-backend sessions managed by the NodeBalancer | count |
| Active UDP sessions | nb_active_udp_sessions | Number of UDP active client-to-backend sessions managed by the NodeBalancer | count |
| New sessions | nb_new_sessions_per_second | Rate of new inbound client-to-backend sessions established on the NodeBalancer per second | sessions/s |
| New TCP sessions | nb_new_tcp_sessions_per_second | Rate of new inbound TCP client-to-backend sessions established on the NodeBalancer per second | sessions/s |
| New UDP sessions | nb_new_udp_sessions_per_second | Rate of new inbound UDP client-to-backend sessions established on the NodeBalancer per second | sessions/s |
| Total active backends | nb_total_active_backends | Total number of backend nodes actively handling traffic across all supported protocols: TCP, UDP, HTTP, and HTTPS | count |
| Active TCP backends | nb_active_tcp_backends | Total number of backend nodes actively handling TCP traffic | count |
| Active UDP backends | nb_active_udp_backends | Total number of backend nodes actively handling UDP traffic | count |
Supported dimensions
This table describes the dimensions available for NodeBalancers. Dimensions are descriptive attributes used to categorize and filter metrics data, enabling more detailed analysis.
| Dimension | API equivalent | Description |
|---|---|---|
| Configuration | config_id | Port configuration associated with a NodeBalancer |
| Port | port | Inbound port that the NodeBalancer is listening on: 0-65535 |
| Protocol | protocol | Inbound protocol used by the port: tcp or udp |
Differences between NodeBalancer's summary stats and Cloud Pulse MetricsThe summary stats in the NodeBalancer application and the Cloud Pulse Metrics dashboard present different types of data. The NodeBalancer summary provides traffic, connection, and backend health statistics based on network interface activity. In contrast, the Cloud Pulse Metrics dashboard offers detailed monitoring data that you can filter and export.
BillingMetrics do not include all billable items on your account. For consistent and reliable reconciliation, use the Billing API.
Updated about 5 hours ago