Submit a ticketCall us

WebinarWebinar: A checklist for planning your Network Performance Monitor (NPM) upgrade

Are you ready for your next upgrade? To help you plan smoothly, join this webcast to learn more about, SolarWinds® Orion® Installer, SolarWinds Upgrade Advisor, Upgrades Guides, Training Videos, and other resources available. We’ll share key upgrade planning considerations, lessons learned from customers with practical advice from SolarWinds Product Experts. We’ll also give practical tips to identify the estimated time needed and resources, how to prepare the business and IT staff for changes, ways to plan for required system changes, and more.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > 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.
    The file to store polled data: C:\ProgramData\Solarwinds\Agent\Persistence\
  • 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