Download PDF
Download page KPI Metrics in Right-Click Dashboards.
KPI Metrics in Right-Click Dashboards
On this page:
Related pages:
- Network Visibility Metrics
- Dynamic Monitoring Mode and Network Visibility
- Flows, Links, and Connections
- KPI Metrics in Network Dashboard and Application Flow Map
- TCP Connection Metrics in Metric Browser
- Node Metrics in Network Dashboard and Metric Browser
- Dynamic Monitoring Mode and Network Visibility
To diagnose a network element, right-click and choose View Metrics. You can troubleshoot the following network elements:
- Tier – The performance chart (top left) shows the rate or application performance outliers on the relevant nodes (Errors and Slow/Very Slow/Stalled Calls) and the Key Performance Indicators for all Connections used by those nodes (Errors and PIE).
- Network Link – The performance chart (top left) shows the rate of Performance Impacting Events for all member Connections of that link.
- Network Connection – You can troubleshoot a Connection from the Connection Explorer or from the Connections tab in a link popup.
You can troubleshoot a transaction from a Transaction Snapshot.
- You can right-click on an application flow and choose View Network Metrics
- You can also drill down to a node where a transaction delay/stall/error occurred and go to the Network tab.
To troubleshoot a tier, link, or connection in the Network Dashboard, right-click the network element and choose View Metrics. The top-left chart in the dashboard shows the overall network and/or network/application performance of the element. To troubleshoot the element, look for correlations between the performance chart (top left) and the other charts on the page.
Tip
You can switch between the linear and logarithmic scale in each chart to best highlight metric spikes and variations. Click on the settings button (top-right corner of the chart to switch between scales.
Right-Click Chart Descriptions
Chart | Description | Default Monitoring Mode |
---|---|---|
Network Impact on Transactions (Tiers) | This chart highlights the possible impact of Performance Impacting Events on the app-transaction outliers (Transaction Errors and Slow, Very Slow, and Stalled Calls shown in the Transaction Scorecard). If you see spikes in transaction outliers and correlated spikes in PIE or errors, this indicates that the network is affecting application performance. Look for correlated spikes in the other charts to identify specific issues and root causes: connection errors, packet loss, retransmissions, high-latency connections, and so on. | KPI |
Host Stack KPIs | Interface errors indicate issues on the node's physical interfaces. See Interface Metrics. TCP Wait sockets can result in significant delays and/or errors for the application or service that relies on that socket. A lot of simultaneous WAIT sockets can prevent applications and services from creating new connections. | KPI |
Network PIE - Contributors | Performance Impacting Elements (PIE) are useful for identifying the location of actual or potential bottlenecks:
| KPI |
Network Errors - Contributors | This chart is useful for identifying network errors that can affect application performance:
| KPI |
Throughput | Traffic throughput for the application of interest on the network element. This chart measures application payload data only; TCP, IP, and other packet headers are excluded. | KPI |
Connection Rate Info | Spikes in this chart that coincide with spikes in slows calls or applications errors indicate that there might be an issue with how the application is using TCP.
| KPI |
TCP Loss (mille) | The number of packets lost (sent but not received) per 1000 packets sent. "Per mille" is a percentage with one additional digit of precision. TCP detects lost packets and retransmits each lost packet until it receives an ACK (acknowledgment) from the peer. Spikes in TCP Loss generally indicate that the network is overutilized. | KPI |
Retransmissions per Minute |
| KPI |
Latency (RTT) Comparison | This chart compares the average TCP round-trip times (RTTs) for different types of packet request/responses.
| KPI |
Connection Lifetime | TCP is most efficient when long, stable connections are used. Connection setups and teardowns are very time-consuming and resource-intensive. The more short-term connections get generated, the worse TCP performance will be because most of the time is spent in creating connections and because of "Slow-Start" in TCP optimal TCP bandwidth is not achieved. | KPI |