Open for Voting
over 1 year ago

Allow For Syslog Product Overlap; Log Manager & Legacy Syslog (w/Kiwi)

The new Log Manager product is a nice tool to have, and I understand that product is the future of the syslog functionality for SolarWinds. However, it would be nice to be able to continue to use the old/legacy syslog tools in addition to the new Log Manager tools. We have more nodes sending syslog than Log Manager can even be licensed for, so we couldn't even go full Log Manager if we wanted. Having said that, if we put 1000 of our most important devices to send syslog using the LM product, we immediately lose 100% of everything else. (unless I'm missing something here) So, under the presumption I have the basics correct, we can either choose to process syslog from 1000 devices, losing everything else, OR we can stay with our current Kiwi setup, being able to process ALL syslog from ALL devices, but without all the nice features of LM.

Why not just keep functionality for both sides? (At least for a while, until LM evolves into a more mature product.) I would love to be able to use LM and all its wonderful features for our core network, while still being able to process all the syslog from our peon level nodes too. I know it's not as simple as flipping both switches to yes, but I can't imagine it being rocket surgery or anything too difficult.

Thank you,

-Will

Top Comments

Parents
  • We have alerts on critical doors, cameras, beam sensors, etc.. and EVERY event needs to trigger an alert. If two people scan through the same door into the data center right after one another both entries need to have separate alert events. Similarly if two different people pass by a camera in the data center within the same 10 seconds both need to be noted by our NOC. 

    I have been testing the new Log Manager and if you have a rule the triggers for the same Camera/Door/UPS/Air Handler/PDU/YourDeviceGoesHere the minimum amount of time that the event will trigger again is 60 seconds AND your NOC has to acknowledge the message in the Alerts Console before it will trigger again ever.

    The old syslog engine triggered every time for every event with very little time lag. The new one triggers once a minute and only for the first event in that minute, then never again unless it is acknowledged.

    The new features are nice and being able to get it into the advanced alerting engine is good but the loss of all but the first alert every minute is a show stopper in our environment.

Comment
  • We have alerts on critical doors, cameras, beam sensors, etc.. and EVERY event needs to trigger an alert. If two people scan through the same door into the data center right after one another both entries need to have separate alert events. Similarly if two different people pass by a camera in the data center within the same 10 seconds both need to be noted by our NOC. 

    I have been testing the new Log Manager and if you have a rule the triggers for the same Camera/Door/UPS/Air Handler/PDU/YourDeviceGoesHere the minimum amount of time that the event will trigger again is 60 seconds AND your NOC has to acknowledge the message in the Alerts Console before it will trigger again ever.

    The old syslog engine triggered every time for every event with very little time lag. The new one triggers once a minute and only for the first event in that minute, then never again unless it is acknowledged.

    The new features are nice and being able to get it into the advanced alerting engine is good but the loss of all but the first alert every minute is a show stopper in our environment.

Children
No Data