Uptime Availability Reports Filtered By Location

You mean taking the minimum uptime of devices at a site and using that to represent the site uptime? That will get super complex real quickly. What if it's a device that doesn't actually impact the site because it's a leaf node and not a branch that the entire site depends on?

This should take the topology knowledge we have and use it to determine uptime by branch. It would even be better visualized by having the branches indicate their uptime. Of course this would require LM spend a little time (a lot of time) improving their topology coverage to catch up with other monitoring tools that have mature coverage for topology discovery.

Right now, it seems all LM wants to do is cover the topology of Kubernetes and improve the icons in the UI. I get that and maybe most of LM's customers are K8s customers, but most of the market out there isn't. They're still using technology their familiar with. And for MSPs like us, we don't choose to use K8s or not, it's our customers. And most of our customers are not using new technology, they're still using simple on-prem networking, hosting their own datacenters. This is the coverage that needs to expand in LM. We've had LM for 2 years and still advertise our mapping/topology features available in LM as beta features, not guaranteed to work or even be correct.