Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Archive > 2017September12 - Cleanup > 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 Gerald.Prado on Sep 12, 2017

Views: 64 Votes: 0 Revisions: 6


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
13:44, 12 Sep 2017


This page has no custom tags.