Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Network Performance Monitor (NPM) > Packet loss and latency values in NetPath

Packet loss and latency values in NetPath

Table of contents
Created by Anthony.Rinaldi_ret, last modified by Eric Bryant on Jul 12, 2017

Views: 39 Votes: 0 Revisions: 5


The packet loss and latency values you see in NetPath likely will not match those values elsewhere in Orion, for example on a Node Details page. 


  • NPM 12.0 and 12.0.1


In the inspector panel, NetPath reports the latency, packet loss, and other performance metrics as they relate to that network path. The probe of a network path to a router will have a certain latency. Elsewhere in Orion, the latency value comes from the main or assigned poller to that node, which is a different path.

Also, Orion uses different probing packets to measure latency and packet loss. NPM typically uses ICMP packets. NetPath uses TCP packets with a specified port as probing packets. When packets traverse the path, networking devices could process ICMP and TCP packets differently, which may result in different latency.






Last modified
15:11, 12 Jul 2017


This page has no custom tags.