Submit a ticketCall us

Training ClassSign up for Network Performance Monitor (NPM) and Scalability instructor-led classes

Attend our instructor-led classes, provided by SolarWinds® Academy, to discuss the more advanced monitoring mechanisms available in NPM as well as how to tune your equipment to optimize its polling capabilities. NPM classes offered:
NPM Custom Monitoring and Polling
Orion Platform Scalability

Reserve your seat.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Store large number of syslogs, traps or logs for auditing in NPM

Store large number of syslogs, traps or logs for auditing in NPM

Table of contents
Created by Malik Haider, last modified by Eric Bryant on Jul 14, 2017

Views: 949 Votes: 1 Revisions: 5


This article provides brief information on storing a large number of syslog, traps or logs for auditing for a period of more than one year, and then running the report later on. 

NPM design is not meant for long term storage of syslog, traps nor logs. Default storage for syslog and traps is 7 days. Fortunately Solarwinds offers a solution via Log & Event Manager.


All NPM versions 


SolarWinds recommends using a more powerful appliance for more demanding environments:

Log Management & Log Analyzer Software | SolarWinds




Last modified