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
  • LM will be expensive “notifications software” if then should replace  my Orion traps alerts

    emoticons_sad.png

    The per node /IP license is not cost effective to SLX type environment with 3000 nodes.

Comment
  • LM will be expensive “notifications software” if then should replace  my Orion traps alerts

    emoticons_sad.png

    The per node /IP license is not cost effective to SLX type environment with 3000 nodes.

Children
  • sja​ Well, I think it's going to get real bad when they shutdown the current/legacy syslog functionality (which has ~12 actions), replace it with a minimal LM version that does NOT do those same actions, AND the minimal LM canNOT be used along with a paid LM license. In other words, when they replace the fully functional base syslog tool with a version of LM that does not do the same basic functions, we would be forced into using a different product (licensed LM for basic features?). AND, at the same time, we wouldn't be able to use a limited license of LM (maybe 150-250 node count) applied to important nodes, while allowing any and all additional nodes to fall into the minimal/reduced functionality. Hopefully they don't force everyone to go all or nothing.

    If they go that way, I'm sure the pitch forks will come out soon after.