kschmalz

This is actually a situation where I've found the Powershell monitors come in handy. I've never restricted them to a certain day, but I have several monitors that will make sure a file only exists during a certain time and then that it does not exist outside of that time-frame. The nice thing is that the monitor is always…

In that case the Nodes table needs to be joined into the query. You could either return all servers, or define which particular one you want to return, as I identified in the code below. SELECT DateTrunc('day',CE.TimeStamp) As CollectDay, N.DisplayName as NodeName, Round(Min(CE.MinStatisticData),2) as MinStat,…

Correct. You would replace that with the name of your component monitoring active sessions.

Tried this without any success.

I haven't taken a long look at the accuracy of this, but it should provide a good starting point to work from. In my case this query retrieves the daily min/max/avg for my component called 'Average Match TAT'. This would obviously need to be adjusted if you have duplicate component names, or are returning multiple…

As Marc mentioned, it is much more helpful to add a descriptive name to each component. Here is an example I have from an application monitor I created for one of our web clusters that monitors the central health pages. I then have my alert definition configured with the following script in the message body: <b>Application…

I have a trigger action that does something very similar to what you are describing. One difference is that I placed the executed program on each server and execute it from the trigger using PsExec.exe on my polling server. It is triggered when any node in my web cluster enters critical status, and drops that server from…

Support provided me with 2 repaired dlls which I imported into my installation yesterday that appear to have resolved the issue. I had to ensure all templates with powershell scripts were set to agentless polling, but have not had any issues since applying the fix.