On Sunday 22 July 2007 16:46, shea_greg at emc.com wrote:
Hi Henrik,
Thanks for the reply. A couple of more things if you don't mind, because I trust you gave me the answer, but maybe I wasn't clear in my question. I've added a little table below that represents what I was asking. I think what you told me was that in Hobbit, if the service does not appear in the table, then it is implied that it will not alert. That's Ok, I get that, but I'm being asked by the pointy hair bosses, why they can't see the exceptions, like they do now with BB and BBGen. If I'm missing something in my configuration, great, please point me in the right direction. If it's not intended to look similar, would it be difficult to add?
I actually prefer the new implementation in Hobbit. To me the info report was very cluttered with exceptions & rules that would never be applied to the device. The Hobbit info alert rule table is much simpler to read, If it isn't in the table - it won't send an alert. Something I am actually looking forward to with my migration to hobbit. My bosses and monitoring customers can understand this simple explanation. I can not count how many times I was asked about alert rules w/ BBGEN and my answer was, "that really doesn't apply to your server, ignore it..."
Sometimes bosses and management ask for things that are overcomplicated and really make no sense at all. Just have to be patient and explain why this is better ;) If you really need this, sure it would not be hard to script up a report to appease management.