Does Nethpath Send Out Specific Alerts When There Are Multiple Probes In Use?

Hey Everyone,

I'm starting to deploy monitoring agents in our branch offices and have the default monitor for example google.com I have it setup on 3 probes right now.

Site A
Site B
Site C

My goal is to get alerted if there is an internet outage onsite quicker than what normally Solarwinds can alert us on our network equipment going down.

So for example if Site B lost internet access to Google.com would i get an alert for just site B or would all three probes need to fail? the out of the box alert just says if the netpath google.com is down then trigger an alert. I'm not sure if I'll need to create a new alert and change the alert to say OR netpath probe Site A, or B or C is status DOWN trigger an alert?

trying to find the easiest method to scale this and avoid having to deploy something like Uptime Kuma at every location.

Thanks for reading!

Find more posts tagged with

probes

NetPath

Accepted answers

All comments

rotto923

Found my answer do the following

* Ensure All objects in my environment is clicked
* Delete the netpath service name condition
* change the status to is not equal to UP

This change will make it so any combination of NetPath and Probe will fire an alert, I would also recommend adding "Condition must exist" and some time to it so you don't get false positives as I have my Solarwinds instance setup in Azure I get false positives all the time to Google where it will go "unreachable" because too many attempts but don't see the issue from an on-prem location.

Hope this helps someone.

adam.beedell

Hi Rotto,

Netpaths, while lovely are inherently a bit slow, there's like 10 min calc duration as default and It doesnt go as low as other methods

If you want speed, you probably want traditional polling at a high frequency or event-based methods, where the event ones are near-instant

There isnt a great way to scale netpaths i'm aware of, you tend not to go beyond 20 per agent, so if you wanted to deploy like 300 you would need to automate agent deployment, then some selection//load balancing thing, then the deployment of a netpath to the new location

That said if you're happy with the current setup then that's what matters

rotto923

Thanks for the reply yeah its not elegant thankfully only need 3 or 4 URLs monitored my first thought ws to deploy 8 different Uptime Kuma instances but that would of been a management nightmare!