robotmk VS Nagstamon

We are using checkmk to monitor 1000s of locations in terms of reachability and performance. Basically you use the checkmk (www.checkmk.com) server as a central site that pings your network devices and your servers (both is important since a slow server doesn't mean "the network is so slow(tm)" ) In Checkmk you get nice graphs but you can also export your data to grafana (which is what we do) to build a smokeping like expirience. Smokeping is a nice tool, but it's rather old and does not scale too well. Checks from your network devices can be implemented using ipsla (cisco?). Theres a plugin for that: https://checkmk.com/de/integrations/cisco\_ip\_sla. If you want to monitor stuff from a (near) user perspective: Check MK supports a distributed setup that allows you to place sensors in differenent locations (if you don't want to implement the full end-to-end monitoring using something like Robot-Framework (https://github.com/simonmeggle/robotmk). If you want deeper network visibility then you could pair checkmk with ntopng (https://www.ntop.org/products/traffic-analysis/ntop/). This way you'll get a lot more than plain RTT and network interface load like ipfix, dpi, *flow, etc...

I just moved from FC35 to 36 (I know, but I have to use the earliest viable release because reasons) and nagstamon stopped working. The window/icon whatnot is always green, status windows not being posted. No meaningful diagnostics, other than:

Hello u/ID100T, I just encountered the same error on my fedora workstation. And when searching for a correction, I saw your post and a github issue about it. There seems to have a correction/workaround : https://github.com/HenriWahl/Nagstamon/issues/877 As the correction has not yet been on an official release, you could try the `latest` repo or install it using the `master` branch.