Skip to main content
The system metrics and network metrics that you can access in CoPilot are captured by the Aviatrix Controller. The Controller pulls the data from virtual machines (instances/hosts) that Aviatrix Gateways run on and feeds that data to CoPilot. Some metrics can be used for triggering actions such as alerting and Gateway Scaling. You can also use metrics to monitor the performance of Gateway hosts. You can monitor performance in CoPilot from the Monitor > Performance page. In addition, with Aviatrix Network Insights API, you can use APIs to analyze the performance and health of your Aviatrix-managed resources in external monitoring systems. See External Monitoring with the Metrics and Status APIs for information about using the Metrics and Status APIs.

About Metrics that are Monitored for Aviatrix Resources

Aviatrix Controller captures system metric and network metric information about the virtual machines (instances/hosts) that Aviatrix Gateways run on. Health-type metric information is also captured for Controller and CoPilot virtual machines. See Global Control Plane Health Alert. Metrics that are monitored by Aviatrix Controller and Aviatrix CoPilot include the following: On the CoPilot Monitor > Performance page, you can select metrics to monitor performance on your resource VMs. On the CoPilot Monitor > Notifications > Alert Configurations page, you can configure how to use the pre-existing set of metrics to send notifications about events that occur in your network, such as performance bottlenecks or other problems. To better understand how notifications and alerts work and how to configure them in CoPilot, see Notifications (Alerts) About Network Events. For more information about integrating Aviatrix metric and status APIs with external monitoring tools, see External Monitoring with the Metrics and Status APIs.

About Percentage Metrics

Several network metrics in the tables below are expressed as percentages (metrics with names beginning with per_). All percentage metrics share the same denominator: total attempted packets per second (rate_pkt_attempted), which is the sum of successfully processed packets (rx + tx) and all failure events across both directions. Because the denominator is bidirectional, a directional percentage (such as per_rx_drop) represents that failure type as a fraction of all traffic, not just inbound or outbound traffic.

Health Metrics for Triggering Notifications or Other Actions

The following health metrics are available in CoPilot. They are listed in alphabetical order, by the name used in the CoPilot UI.

System Metrics for Triggering Notifications or Other Actions

For Aviatrix Controller and Aviatrix gateways, you can configure alerts based on the following system metrics. Aviatrix gateways report live Linux system statistics (such as memory, CPU, I/O, processes, and swap) for the instances/virtual machines on which they run. Metrics are listed in alphabetical order, by the name used in the CoPilot UI.

Per-vCPU Metrics

Starting in CoPilot 4.32, the following per-vCPU metrics are available through the Metrics API. These metrics provide CPU utilization broken down by individual virtual CPU core for each gateway, enabling identification of single-core bottlenecks that aggregated CPU metrics may mask.

Network Metrics for Triggering Notifications or Other Actions

For Aviatrix Controller and Aviatrix gateways, you can configure alerts based on the following network metrics. Metrics are listed in alphabetical order, by the name used in the CoPilot UI.

Cumulative Counters

Cumulative counters represent running totals since the interface was last reset. CoPilot uses the difference between consecutive readings to compute per-second rate and percentage metrics.

Per-Second Rates

CoPilot computes per-second rates from cumulative counter deltas between consecutive collection intervals. Throughput rates (rate_sent, rate_received, rate_total) are reported in bits per second.

Percentage Metrics

Percentage metrics express a specific failure rate as a fraction of total attempted packets. All percentage metrics use the same bidirectional denominator: rate_pkt_attempted (see About Percentage Metrics).