Logging to DB - size growing rapidly

kahlif

So, I am eval'ing syslog server to implement at our company.  Our final installation will have about 20 devices and 50 linux servers logging to it.

To test, we have 2 devices and 6 linux servers logging to it.  It is averaging 2700 msgs/hour.  Currently it is logging *.* from the linux servers, but we will be more selective in a final deployment (although this is a good indicator of final load).

I have the server set to log to my central MSSQL server.  My concern is that the DB is growing at about 9MB/day.  This kind of growth is unsustainable in the long run for us.

Am I missing somewhere that I can configure compression/purging on the DB, or should I log to flat file and only log to the DB what I really need long-term data for?

Thanks!

Kuz

Short answer is yes, you should log to file, and only log to DB what you really need long-term.

That said, Kiwi Syslog Server also provides scheduled archive functionality, so that log files (on disk) are current, and log files that are too large, too old, etc. are archived (ie. compressed and stored elsewhere).

Check out this from the help file:

www.kiwisyslog.com/help/syslog/archivetask.htm
www.kiwisyslog.com/help/syslog/howtheschedulerworks.htm