Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Separate syslog and trap records from Orion/NPM database

Separating NetFlow records from the rest of Orion's data was a great thing that vastly improved performance for us as we generated over 80,000 flows per second. Separating syslog and SNMP Traps would also help performance as our SQL server is busy writing over 1,000,000 trap records and over 40,000,000 syslog records per day. We have had to reduce the syslog collection due to poor database performance (1 and 40 million records is after we stopped some logging). This limits syslog monitoring effectiveness since some alerts no longer work as we diverted the feeds to Splunk. At a minimum, put syslog and Trap messages in a separate database so I can place that database on a separate drive, but even better would be to allow a separate SQL Server so I have the option to distribute the database workload across two SQL servers.

Find more posts tagged with

Status: None

Comments

sja

Orion/NPM is not log&event software by definition.

I for sure will not say "don't make the syslog and traps service better :-)".

If you want use Orion in bigger shop you need other tool for syslog and sometime traps.

You will get much more from your NMS by doing all that log correlation out side of Orion.

and den forward that 1%-2% that you need to look at.

Try one of this tool to your syslog

Kiwisyslog

LEM

Splunk

Syslog-NG