anthony.os

The test do run every 3 minutes. As I stated earlier, I exported the actual statistics using SQL query/reports and it shows the test being separated by 3 or 4 minutes which guarantees I have must have 3 consecutve instances exceed threshold to trigger an action. Now when I rewrite my alert rule to note use "Transaction…

There are several different transactions that begin with "LWEB02"; they each run every 3 minutes. The trigger condtion must exist for 10 minutes before an action is taken; which means a given transaction must exceed a duration of 10 seconds at least 3 times. I ran a SQL query/report to show the actual transaction times for…

wiszm23 - I now understand that alerts on child will only show content when active alerts exist. But why did I receive an email notification (alert was triggered and not supressed) when the parent node was down in my example? There are two ways to supress alerts; through dependency and through the alert supression setting…

Thanks for the tip, but I have a follow up questions. What if I have 300 transaction tests, but I only want the alert condition I described to apply to 200 of them (and perhaps the other 100 tests would have different rules for alets applied to them)? What would be a way for me to use some sort of "wildcard" that would…

I want the alerts to re-trigger; but at a frequency that I can define. This way I will know if the issue was addressed and be reminded when if it was not. Otherwise there will cases where an alert gets sent, it gets missed or forgotten, and never addressed. I have the "-2" condition for MS Cluster disks which don't show a…

The OS for this system is Windows 2003 SP2. The SAM version is 5.5. I'm not sure if the polling method was changed from SNMP to WMI; this is a new installation and we used the network discovery to add the majority of hosts. Since you asked about the switch, I manually deleted the node, and re-added it as WMI from the…

I setup a basic test using 2 non-production nodes. I made SERVER_A the parent node, and SERVER_B the child node. I shutdown SERVER_A and was alerted that it was down. Now I expected that any issues with SERVER_B would be supressed if I shut it down given it's parent SERVER_A was down. I proceeded to shutdown SERVER_B, and…

The drive is selected; it will report the correct statistics except for the condition where the drive is completely full. I was able to reproduce the problem on Windows 2008 R2. I'm going to try another Windows 2003 SP2 machine. I do have a case opened with support and they have requested the diagnostic log which I will be…

I have a group call it "SITE_A" that contains several nodes, some of which have application monitors on them. I nested these as children under the router interface to this site as the parent. When I view the option "alerts on child" it does not show anything. We don't have any special alerts for the nodes. Basically we…

SERVER WEB01 has tests WEB01-TEST1, WEB01-TEST2, and WEB01-TEST3 WPM tests run against it. SERVER WEB02 has tests WEB02-TEST1, WEB02-TEST2, and WEB02-TEST3 WPM tests run against it. If I create a single alert that says: Transaction name begins with WEB Duration greater than 10 seconds If condition exists for greater than…

This is actually working correctly now; I'm not sure what changed. For a couple of days all the repeating reports were the same even though the amount of space changed.

Here is the line in the message: Current space available: ${VolumeSpaceAvailable} It appears the value for the VolumeSpaceAvailable variable is remembered until the condition is cleared.

Thanks for the tip. It appears much of the information is kept in SQL views. I had been looking strictly at tables for all the information.

I left the monitoring in place and this is what happened (keeping the same settings from my original post): The first set of low disk space alerts get triggered at 00:00:00 (emails sent). These are non-critical systems we want to stay in the trigger condition to test the alerts behavior. The next set of email alerts get…

It shows SolarWinds at the Catalog under the database settings. Any idea where the other database would have come from? I don't recall having the option to specify the database name, so most likely it is the default value that is in place.

It was coming from the Basic Alert Manager; thanks.

Will do; thanks.

Just wanted to add that this node is monitored by WMI and not SNMP.

TRIGGER CONDITION Type of Property to Monitor: Node Trigger Alert: Last Boot has changed