Monitor NodeBalancers using Cloud Pulse
Akamai Cloud Pulse provides real-time insight into the performance, availability, and reliability of workloads running across your cloud environment. It brings together metrics, alerts, and logs to help you understand system behavior, detect issues early, and maintain the health of your applications and infrastructure.
Metrics are the first monitoring capability delivered for NodeBalancers. Alerts and logs are planned for future releases.
Limited availability
Akamai 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.
Metrics (Limited availability)
Metrics provide time-series data about the service's usage, performance, and operational behavior. Metrics are automatically collected by Akamai Cloud Pulse and can be viewed in dashboards, queried, exported, accessed through the Linode API, or used to define alerting thresholds.
Key features include:
- Automatic metrics collection. Akamai Cloud Pulse automatically collects and stores metrics for NodeBalancers
- Visualization and analysis. Explore performance using metrics dashboards that present key indicators and trends.
- Metrics export. Export metrics for analysis using external observability tools. The Akamai Distribution of the OpenTelemetry Collector for Akamai Cloud Pulse exposes metrics for ingestion by your chosen visualization and analysis tools.
- Programmatic access. Retrieve metrics using the Linode API.
Supported NodeBalancer Metrics
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_trafic_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 |
Dimensions
Use these dimensions to filter or group metric data.
| 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 |
Billing
Metrics do not include all billable items on your account. For consistent and reliable reconciliation, use the Billing API.
Differences between NodeBalancer's Summary and Cloud Pulse Metrics
The summary 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.
More Information
To learn more about Akamai Cloud Pulse monitoring capabilities, see Monitor Cloud Services.
Updated 1 day ago