Thank you, Acy Forsythe.
I see: I assumed that Kiwi syslogger and the syslogger in NCM were the same product.
As I am reading through the forums, I'm seeing mention of people who run both Kiwi Syslogger and the NCM syslogger.
I am going to continue to search for answers, and post any that I find here.
So, based upon your answer and further reading, the answer to my first question is:
1. Kiwi Syslogger and the Syslogger that is part of the NCM suite are two different programs. Kiwi stores logs as a flat file. The Syslogger in NCM stores logs in the NCM SQL database.
So, the question then becomes:
- Is it possible to use the NCM Syslogger to monitor Cisco Devices in the longterm? We purchased the package with that capability in mind, and not simply alerting.
- Is it better to utilize Kiwi as the front-facing syslog tool while forwarding certain syslogs to the NCM?
I ask, because it seems counterintuitive to me that a tool with a SQL backend should be less better equipped to offload and backup syslogs than a flat-file tool.
But there may be elements of the discussion I am not aware of.
I personally move warnings and above to another DB for posterity, and wipe out any lower priority syslog messages from the main Syslog DB.
Is there anything in the documentation for NCM syslogger to facilitate this kind of backup/pruning of the database?