I just want to set up an alert for a node down in a certain group. I've placed a number of nodes in a group and would like to send a certain notification if a memebr of that group goes down. What would that alert look like?
Jeff
via web...edit nodes --> custom property editor --> create a custom property against node with a name that suggest it will be an email (for example CustomerEmail) --> populate email addresses for nodes as desired.
(You can also select many nodes in Manage Nodes via checkbox and then edit the nodes. But the custom property editor is pretty cool so check it out too--it's a lot like working with a spreadsheet.)
trigger condition
cpu > 90%
CustomerEmail=jeffreyc@yourcompany.com
action
send email to ${CustomerEmail}
separate alert
trigger condtion
volume > 78%
CustomerEmail=d09h@mycompany.com
Alert on Group
Trigger Condition
Group Name is equal to CertainGroup
Group Member Group Member Status is equal to Down
I thought there was a default group member down alert already built in.... it would look like what purdue98 put up.
jeffreyc, group also needs to be defined (advanced option on groups):
Status Rollup Mode: Mixed status shows warning
or
Status Rollup Mode: Show worst status (from your post this seems like what you're looking for)
Leaving this set to 'Show best status' will keep your alert from acting the way you desire.
I did get this working by doing the above and setting the alert like this
How could I do this type of alert for cpu and disk utilization while still using members of a certian group.
jeffreyc, when I set this up on my server to check out how it would look, I kept coming to the conclusion that I would make two alerts. One for Node and one for Volume. I also don't see that group approach helping. I see custom properties helping here. Just my thoughts on how I would do it after mocking it up on one of my environments.
Groups are better for some things than custom properties are. I just don't see them being useful here. You could certainly use custom properties and then (if even necessary) make a group dynamically populated (dynamic query) by WhateverCustomProperty=Something.
If you intend to have an action, then I suppose an alert approach applies. If no action necessary, polled values could simply be displayed on a web page. Without utilizing alerts, CPU information can be displayed (filtered for some %), and volume information displayed (filtered for some %) , and the page itself limited by Group.
Do you require an action (email perhaps) or just want to show content on a web page? If so, a volume alert could be created--action is send a web page (that shows what I described in paragraph above). And a node alert created for CPU--action is send the same web page.
Yes I definitly need to perform and action which is to send an email. I need to some how seperate nodes by groups that are resposible for them and in turn should recieve the notifications for them. For instance we might have 25 different emial groups that our 700 nodes would be divided among. I have alerts for cpu, disk , app monitors you name it already configured but I need a way to send them to the right group email.
If the same audience would receive a volume alert as would receive a CPU alert (no situation where one audience expects email on server XYZ CPU but a different audience needs email for volume on server XYZ), I would leave groups out altogether and handle via custom property.
Create custom property (node custom property and not volume or any other flavor) CustomerEmail. Populate that property jeffreyc@yourcompany.com or d09h@mycompany.com. You can leverage that property in your Trigger Condition as well as your action.
I've done the second half of what I just described a few years ago (custom property is an email address...send email to that custom property ${CustomerEmail}). I sent emails to a custom property because I used to have dozens of emails in there and one day hit the 255 character limit of the Alert Manager field email address field. So I created three properties of (text type and that size) to contain customer email addresses and put some in cc line. I don't think there's a 255 character limit anymore, but the same thing can be done for the flexibility if affords.
So if I went that route I would then have to add a custom property to each node that would identify it with whatever group was resposible for it and in my trigger I would add that as a condition right?
Which brings me to my next question. What is the quickest way to add a custom property to multiple nodes at the same time? Can that be done thorugh the web
