Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

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: 932 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