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
  • I have to agree with you on this one!  I spoke with our SW account manager at length after I demo'd LM about this exact issue.  We have over 1000 nodes sending traps and logs but at any given time we only look at a handful and have alerts set up on only a few.  I do like the functionality of LM with integrated alerts and such but the cost is very prohibitive to do large numbers.  What I would like to see is either keeping both tools or combining them a little more, ie license per node for ones that you can alert off of but still collect all the others into the database and allow searching and viewing of the other traps / logs for trouble shooting purposes. 

Comment
  • I have to agree with you on this one!  I spoke with our SW account manager at length after I demo'd LM about this exact issue.  We have over 1000 nodes sending traps and logs but at any given time we only look at a handful and have alerts set up on only a few.  I do like the functionality of LM with integrated alerts and such but the cost is very prohibitive to do large numbers.  What I would like to see is either keeping both tools or combining them a little more, ie license per node for ones that you can alert off of but still collect all the others into the database and allow searching and viewing of the other traps / logs for trouble shooting purposes. 

Children
  • justinb@city.ketchikan.ak.us​ I think that idea would be best for everyone. A good middle ground. Having the ability to use licenses for more important/critical nodes while still maintaining the basic syslog functionality that exists today for any remaining nodes should cover all bases.

    I sometimes feel bad for some of these decision makers, as I understand they need to make money. But taking away core functionality of a program that has been around for so very long, and replacing it with a shiny replica at a steep price, well that just doesn't feel right to me. And the same goes for forcing folks into the all or nothing choice.

    They knocked it out of the park with NetPath, PerfStack, and a few other new features. Those things came out and added more value to the bottom line, perhaps compensating for some other areas in which they have been falling behind the competition.