Comments
-
it is Cisco ASR 920, should I open ticket with SolarWinds support ?
-
Those readings are from the device itself and matches with the NPM, the different is larger interval on SW, but still it is less than trigger condition.
-
It is still present on the "Active Alerts" page which is weird ! because the trigger condition is no longer true and this supposed to clear the alert ! Triger/Reset conditions: Current CPU load: it is less than 70 thanks for the reply .
-
I edited the query to output alerts for only node down, in that process I added the same thing that caused the error that prevented the row to be displayed when it get acknowledged, thanks to you I could detect that which was (nolock with joints) , thanks a lot ....
-
I appreciate your support , I tried your suggestion and it is still not meeting our teams requirements, the rows for each alert disappears as it get acknowledged when the actual issue is still there . what they asking for t have a widget that shows those alerts during that day for example "node down" that shows real status…
-
@"bogdan.stan" Thanks a lot I was using wrong widget type.
