I have a few APM HTTP Form login monitors that have external nodes they use. These nodes are not pingable so they always show down. It would be handy if we could have an "unmonitored node" for this type of situation.
With 9.5 we added a new method to define a node called external for APM so you have a node to associate it to, but we don't ping it etc. so it won't show as down, but external
External shows as down.
we are confirming now, but this appears to be a defect, this should not be showing as down
Hi,
You can do a little hack to get around this until we fix the bug in the code. In the file:
C:\inetpub\SolarWinds\Orion\NetPerfMon\Resources\NodeSummary\DownNodes.ascx.cs you will see a line like:
string filter = "Status <> '1'";
To just remove External nodes from this change it to:
string filter = "Status <> '1' AND [External] = 0 ";
As always, back up this file before making any changes.
The next time you run the configuration wizard on the website, your change will disappear. I have logged a bug for this in our system and we will fix it in a future release.
Thanks
So after some further discussion around here and a little investigation, we have determined that we have unfortunately two "Down Nodes" resources. One is under the "Node Lists" group and is actually filtering on everything that is not up (Unknown, Warning, Down, External, Unmanaged). The second one under "Summary Reports" is a listing of all the nodes that are actually Down.
Our actual change is going to be in the naming of these two resources to accurately reflect this difference.
Hence, you need not change the code behind for this fix. Instead I recommend editing the resource and adding the custom SQL filter
[External] = 0
then you should be good to go.
