Comments
-
You can also restart the NetPerfMon service to unstick the CPU monitor.
-
You can create an alert when an interface goes into an unknown status, but the node status is up. If you are monitoring the loopback on each node, you can make a standard alert on the interface type. That would prevent alerts out on other interface issues.
-
I think the biggest problem with SolarWinds support is that there isn't a central knowledge base. I have gotten various answers to the same question multiple times. The thing that really pisses me off is when they guess!! Also, some reps don't even read your question, they give some canned answer that has nothing to do…
-
If you are talking about a Microsoft cluster, it can be done like any other node. I monitor each node's local drives only, and monitor the shared disks through the virtual cluster name. Are the drives not showing up when you list resources? Is this a 2003 cluster?
-
Have you had any luck with your conversion? I have had issues with my conversion as well and wondered if you were successful. Thanks.
-
This should work. We use start and end times and to suppress alerts during that time. We also use a patching field that when it is populated the alerts won't trigger. If you can paste a screenshot, I might be able to help you.
-
Three years ago SolarWinds support gave me a special suppression dll that allows for suppressing a node based on the status of a node specified in a custom property. It was extremely helpful in our environment since we were monitoring 1000 routers and the devices behind them. I was going to explain how to configure the…
-
Do you want the node unmanaged or just the alerts suppressed?
