First of all, I don't come from a Tivoli, OpenView background , I have never touched the commercial network monitoring tools and I`m not a network guy . I'm an infrastructure guy whith a focus on Open Source platforms so I have been using Nagios and more recently Zabbix, Zenoss etc for the better part of the last 2 decades in large to very large environments.
My syslogs go to a central (r)syslog)-ng) server where I frequently abuse grep. So If my experience with RiverMuse is not what it should be , there's work to be done on both sides ;)
So When looking at my Rivermuse setup (in a VirtualBox FC9 setup) my first tought is "Those Rivermuse folks will really need to explain me what their tool is all about .. as to me it's just a fancy colortail integrated with snmp traps."
Hopefully it's not just that and it all becomes clear in a couple of days .. Apart from the FC9 annoyancy there is the frequent Unresponsive script errors.
And those I fear will be the real killer problems for RiverMuse
On the other hand, RiverMuse does good job in displaying the actual events in your network and following up the actions that one ... after a while you'll get a good overview of the actual issues as opposed to all the relevant events
I've dropped RiverMuse into my blade test setup (more on that subject later) and I`ll be keeping a look on what I can learn from it but the dreaded Unresponsive scripts that I know so well from Bamboo really need to be fixed :)
Well time will tell :)