Quantcast
Viewing all articles
Browse latest Browse all 2141

Re: Syslogger - Questions about SQL database, retaining logs for long periods of time, and remote connectivity

Hello and welcome to the community.

 

I don't have all of the answers for you, but I think I can point you in the right direction...

 

1. The syslogger that is part of Orion is not really Kiwi Syslogger. I'm really not 100% certain what features it contains in comparison with Kiwi, but I would imagine that by default it does log to the Orion DB. Kiwi on the otherhand logs to flat files by default and has to be configured to report to a DB.

 

This may also be a more versatile solution and I'm aware that numerous Orion users utilize both Kiwi and Orion. Simply have all of your devices point to Kiwi, possibly for some added control and log management options, and then have Kiwi forward logs to the Orion Syslogger based on your criteria.

2. Again, I'm not 100% sure what administrative control over the DB you have with Orion, but in a normal SQL Server cluster environment, I would setup maintenance jobs to do a daily/weekly/monthly archive (whatever the DB can handle). I personally move warnings and above to another DB for posterity, and wipe out any lower priority syslog messages from the main Syslog DB.

 

Fine-tuning what to keep though is something that should really be done at the device end. Although Kiwi is capable of limiting what actually gets logged, I'm not sure if Orion's Syslogger can be configured that way.

 

For more specific information from users who are utilizing Orion, I would try asking in this space:

http://thwack.solarwinds.com/community/network-management_tht/orion-network-performance-monitor

 

Acy


Viewing all articles
Browse latest Browse all 2141

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>