Submit a ticketCall us

AnnouncementsSystem Monitoring for Dummies

Tired of monitoring failures disrupting the system, application, and service? Learn the key monitoring concepts needed to help you create sophisticated monitoring and alerting strategies that can help you save time and money. Read the eBook.

Get your free eBook.

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: 958 Votes: 1 Revisions: 5

Overview

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.

Environment

All NPM versions 

Detail

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

Log Management & Log Analyzer Software | SolarWinds

 

 

 

Last modified

Tags

Classifications

Public