Comments
-
I actually set the alert delay to 60 minutes for CPU and Memory... transient spikes are notorious issues to run to ground but sustained high usage is indicative of a sizing problem with a server... bearing in mind that certain applications, SQL and Exchange primarily, are just hogs and will use everything you throw at…
-
Actually it turned out to be a SNAFU with a view....
-
Hmmm... so we have individual Windows servers for each of our polling engines (Server Application Monitor, Network Performance Monitor) running 2008R2 with 8 cores and 16GB of RAM... also separate servers for Network Topology Mapper, IP Address Manager, Storage Resource Manager, Alert Central, the DB server... so a big…
-
"Unmanage" all the nodes for the expected time window when you will be doing the upgrade (obviously before you start the upgrade).. may want to add some time on the back end as a "pad"... that should do the trick for you...
-
* Often * Multiple Tabs, screenshots, email...
-
There is also an option in Advanced Alerts to "hold on" to an alert of "X" amount of time before sending out the alert... it is on the Trigger Conditions tab and its a check box for "Condition must exist for more than"... I use it for several different things... for example a node must be down for 6 minutes (which equates…
-
Where do you want the yellow to "show"... in the pop up when you hover over the server.. in the Node detail page where it shows memory usage?? Also if its a database server that level of memory usage is normal... Windows (Microsoft SQL) or Linux (Oracle SQL)?
