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
Store

Syslog Database

bashley

My undestanding on the syslog messages is that they get dumped in the same database that Orion uses for polling.

1. Is this correct? Do the syslog messages get dumped in the same database as the polling statistics reside in?

2. Is there anyway to move the syslog database to a seperate machine and point Orion to this system?

Thanks!

Find more posts tagged with

syslog

Accepted answers

bshopp

torrielw,

Not sure if you aware, but we recently acquired Kiwi Enterprises (http://www.kiwisyslog.com/), in which their their key product is Kiwi Syslog.

With Kiwi Syslog you can store Syslog messages to a flat file and then configure rules within Kiwi to forward specific Syslog events up to Orion. Also, the ability to act as a transparent proxy is a feature of Kiwi Syslog Server today as well.

Denny talks further about Kiwi and our plans going forward in this thread -

All comments

I can tell you that

1) Yes, syslogs are in the same database as the orion database, with five tables: SysLog, SysLogActions, SysLogFacilities, SysLogRules, SysLogSeverities.

2) I can't think of a way this could be supported or configured, maybe someone else has a trick but I doubt it's possible.

bashley

Thanks for the info, that is helpful. I am using the SolarWinds event log forwarding to monitor and alert on services for some of our applications. In addition to the Syslog messages from network devices I am just worried about the growth of the database as I begin to monitor more and more syslog messages from systems in order to monitor services. Does anyone else do any service monitoring?

I'm actually surprised at how small my syslog tables are, just under 20 megs... You might do fine.

Network_Guru

You can set the Syslog retention to something like 14 - 30 days & that should keep it in check.

Other than that, if you have a DBA maintaining your Orion DB, you could have them write a stored procedure which moves the Syslogs into a separate DB (possibly on another server).
You'd have to rewrite the Syslog.asp file to connect to this new DB and use ODBC to connect if it is on another server.

torrielw

The syslog server was once a separate server. I would like to see it separated again for longer retention of data and less impact on the netperfmon db.

bshopp

torrielw,

Not sure if you aware, but we recently acquired Kiwi Enterprises (http://www.kiwisyslog.com/), in which their their key product is Kiwi Syslog.

Denny talks further about Kiwi and our plans going forward in this thread -