Comments
-
This has been a big issue for us also. We are trying to move to Solarwinds as our primary trap receiver. Not being able to define specific variables has forced us too look at other options.
-
we are using an exe we created that calls our perl script. This sends all the trap info to the script, and the script parses everything from that side. It is not the most efficient but it has worked for us. scriptname.exe "${Message}" In the upcoming version I believe it will let you use the different variables
-
We have been using APM for a little while to perform application monitoring. What I have found works fairly well regarding the expertise question is to engage the application groups. I initially tried simply setting up a meeting and asking what they cared about and received almost no good input. So I took a different route…
-
I used a workaround. it's not the most elegant solution but it works and is better than scrolling through our list of 875 windows servers. My workaound - As a workaround I added a custom field that I named "Edit_Flag" The I added the "Edit custom node property" to the node details page. So now we can search for a device…
-
How long until we get to use this? We are having mass issues right now with using the trap receiver to the point we have begun looking into other vendors for this part of our toolset. Everyone of these would be a big deal to us, specifically #1 and #5.
