rotto923 ✭✭✭✭✭

Hi @vinay.by, Sorry for not seeing your response sooner. I just did check it does pull some useful but a lot of it looks to be massaged as its pulling "206" SSIDs (we have 3) and doubled our number of APs etc. This is useful though I'm going to go through and look at the dashboards as I didn't even realize this was a…

Is there any ETA on when this is going live as the recommended version and no longer be release candidate? I really want to upgrade but I don't want to put an RC into production. Thanks,

This new UI is garbage the old one was so much more usable. A few things I found 1. The back button doesn't work there is no way to go back to a previous view if you click the wrong thing you have to start all the way over 2. Groups aren't adhering to the correct parent group I've opened a ticket about this 01982592 3.…

Hey Travis, use the ICMP only monitoring method. If you don't have a large environment in Azure you'll need to setup a NAT gateway or an NVA of some sort or you'll be stuck with putting a public IP on your box if you do that I would just lock it down with the network security group only allowing exactly what you want out. 

This is what I have setup works. 

I ran into this same issue and was given a band aid workaround fix but if you add new objects you'll need to repeat these steps. Ultimately I was told it would be best to move to the modern dashboard. Am running 2024.1 1.) Navigate to this location on your Primary polling engine or Additional Web Servers:…

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!

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…