ZakWooldridge

I thought I was going to have to write custom queries or understand the syntax of the variables but no, you were right to nudge. It was actually very simple. As Vinay.by said "Alert variables are linked to the type of object/alert that you create". So even if you set up a useful alerting template for node based alerts,…

I understood all of that up until the end. Sorry, I am new to SWQL. Essentially, build a custom variable that determines the value by looking at the parent node and then to the table / row that contains the custom address data? 

This does make sense. Annoyingly, I had to create an interface based alert as trying to trigger based on utilisation does not work with a node based alert. 

Thank you, I am still trying to get my head round the duplication. I have tried limiting the filters as much as possible but I think that Netflow has possibly been misconfigured as no matter what I do, it still shows that exactly 50pb are egressing and ingressing in the past 24 hours. Firstly, that figure is ridiculous,…

PercentLoss > 10 Like this

This is within the "Edit Resource" menu of the widget. The section reads: Filter Nodes (SWQL): PercentLoss<>100 Filters are optional and can be used to limit the list of Nodes displayed. This is an advanced feature. We recommend you have a basic understanding of SWQL Queries. If I use say "status = 2", the filter works and…

Thanks, Mr Holmes. I was thinking IIS apppools or something along those lines but my IIS knowledge is limited. Thank you for the confirmation and more accurate indication of the issue. 

That page fails to load when I go to it. 

Sounds possible. The latency is above the failure threshold when performing a test. Though pinging between the two pollers show <50ms. Will investigate this further. 

Thank you. Removing and re-adding a node seems to have uncovered something even more concerning. When I try to add the node, I get "Test Failed. Exception of type 'SolarWinds.ApiProxyFactory.TransientApiProxyException' was thrown." It looks as if the main poller cannot "talk" to the secondary poller. Very odd, as I can see…