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 > Network Performance Monitor (NPM) > Agent based monitoring: Buffering FAQs

Agent based monitoring: Buffering FAQs

Table of contents

Updated April 20, 2017


Agent based monitoring is not network dependent. This means that the agent will run as long as the device is running and stores data locally until it can be forwarded to a listening server. This article answers questions regarding buffering and also provides monitoring tips.


All NPM versions


  • How long can Orion lose network connectivity to the agent before data loss?
    The agent caches polled data for a period of 24 hours. After 24 hours, data is lost on a first in, first out basis.
  • How big is the buffer?
    The buffer size depends on the amount of data you are polling.
  • Refer to the SolarWinds MONITORING 101 post in Thwack for further details.


Last modified
11:32, 22 Jun 2017