Comments
-
This is something that we are looking for as well. Although we have a scheduler built into our scripts that only reports what we want when we want, SAM is still collecting information every 5 minutes (our polling frequency). We would like to keep our information so that we do not have to filter out so much useless…
-
We are attempting something to display component alert history, and would benefit from being able to pass the ${ComponentID} variable into our queries. Even if we would be able to start from the Application level would be beneficial.
-
Have you heard anything more regarding this issue? We were using a similar method to alert our monitoring team and it has not been working.
-
You still can. You can have the SQL query that you have and have that as the trigger for the alert. The alert will run that query every time you want it to (5 mins is what I usually use for SQL alert triggers) and will alert if any results are returned. If you are not comfortable with this I can try to assist with finding…
-
For clarification is this a True/False property? If so you may have write the alert trigger as a SQL Query that combines the audit events table with the container table that records the custom property changes. In the alert definition I do not believe that it will translate the SQL macro that you are trying to use. (Anyone…
-
I have already gone through most of the support pages (Including this one) and they have not helped in any form.
-
If this is the only custom property on your groups you could try something like I have below for your alert. You can also add another line like the bottom one that would read like this to further narrow the search:
-
If the teams are server specific, then you could create a custom property for Nodes called something like Alert_Team. Then you could call this in the alert email addresses for your alert using this formula in the "To:" field: ${N=SwisEntity;M=Volume.Node.CustomProperties.Alert_Team}. This will allow your alert to be…
-
I have found a way to display this on the component page in SolarWinds by doing the following: * Have the alerts write to the NPM Event Log * create a custom query resource on the view * use this query to display history SELECT E.EventTime, N.Caption, C.Name, E.Message FROM Orion.Events E JOIN Orion.APM.Component C on…
-
Forgot to mention that I am able to run the powershell scripts locally on the poller without any issues.