The network agent does not collect any Connection metrics in KPI mode (the default setting). You can change the Dynamic Monitoring Mode on a network agent when you need to diagnose a node or network path that is monitored by that agent.

Example Workflow

After you complete the initial setup, you can set the Dynamic Monitoring Mode on individual network agents as needed. An example workflow might look like the following:

The DevOps team for a large enterprise monitors its IT infrastructure using network agents on critical servers. All agents are initially set to KPI mode.

The Network Dashboard shows a spike in latency on a network link between tier-A and tier-B.

A DevOps team member does the following:

Sets the network agent DMM on the tier-A and tier-B servers to Diagnostic.

Collects KPI metrics for the Connections between the tier-A and tier-B nodes.

Identifies one high-latency connection between nodes TA-N1 and TB-N3, based on the Connection KPIs. The KPIs for all other connections are within acceptable bounds.

Sets the network agent DMM on TA-N1 and TB-N3 to Advanced Diagnostic and the DMM on all other agents to KPI.

Notes a set of spikes in Nagle delays on this Connection. These spikes correspond to the latency spikes she noticed on the network link.

Reconfigures TCP on the two nodes and monitors the Connection. The Nagle's and latency spikes no longer occur.