Comments
-
Is there a performance penalty for using the SQL query vs the macro? If not, I'm fine just using the query.
-
I couldn't get ${APM_ApplicationCustomProperties.MyProperty} to work so let me know if works for you. I still had to use the SQL query, but I was able to do so without the ":" trick that was required previously.
-
***Update*** I got it working, but not using the variable above. Instead I used the SQL query from your other suggestion. However, I did not have to add the ":" in the custom properties as stated in the article. I just placed the following line right in to the "To:" field. Perhaps this is what was fixed in 6.1?…
-
I'm on 6.1 but I'm still just getting the variable back in both the To field and message body. Let me post a picture of my application custom property, maybe I'm missing something obvious. Here is my variable: ${APM_ApplicationCustomProperties.NotificationTeam}
-
That part seems pretty straight forward. What about breaking WMI out to its own svchost.exe process? Can it be reversed? I can't think of any reason that would cause a problem down the road but you never know.
-
I like the idea, but I'm having trouble getting the variable to translate in the "To:" field. My custom property is on "Applications" and the "Property Name" is NotificationTeam. Shouldn't my variable then be: ${Application.NotificationTeam}
-
This works great, just curious if anyone knows how to back it out once it's in place. I can't think of a good reason to do it right now, but we always like to have a rollback plan.
-
That information is very helpful. I'll remove "unknown" from the alerts and see if that solves the issue. Thank you for the quick response.
-
I use the n_mute but I have only changed the attribute one server at a time. How do you change the properties on all of the at once? Custom property editor? If so, is there a way to schedule it?
-
Also, what is the benefit of writing the mute logic in to the trigger condition? Wouldn't it simplify things to use the alert suppression field instead?
-
This thread hasn't been touched in a while. Does anyone know if this has been addressed in SAM 6.1?
-
For Windows boxes I found that you need to find and install the correct version of the HP Insight Management WBEM Providers for Windows. There are seperate versions for 2003, 2008, x86, x64, ect. Once you have everything installed correctly you have to click the "List Resources" button on the SAM page for that server and…
-
Update: Our SQL DBA wrote a stored procedure that flips all the n_mute attributes on and off and then wrote a little web interface for it so the admins can set the schedule. Currently it's all or nothing but he's working on a grouping function for us. Once nice side affect of this method is that everything is still…
-
Has anyone confirmed this working? I just tried on 6.1 and I'm still getting the variable back.
-
We have several members of our team adding nodes and I can easily see on of them forgetting to set this property, so the way the alert is written "If n_mute IS NOT YES" then all new nodes would default to no alerts. I see this as a potential problem. I was going to ask how you mange the introduction of new nodes since…
-
I think I have this figured out, but I am still waiting on an actual event to test it. To make it work there are two pieces. First you have to have a service monitor on the service you want to restart. Once you have this you can drill down to that service and get the application ID from the browser link. From there you…