We have 1000+ nodes and would like to use the parent/child topology for visibility. We are 80% complete but two issues are causing trouble:
Some nodes in the parent/child topology can not be moved because they snap back to previous position. Other nodes work fine. Is there a workaround? Deleting the host from /var/check_mk/topology/configs fixes the problem temporarily but it keeps coming back. This affects in particular hosts with double links and circular links.
The view is cluttered. We have put most hosts that are not interesting under a parent so that they can be hidden. Is there a way to collapse a node so that children are not visible? When opening parent/child from a specific host the host can be collapsed, but not when opening from monitor / parent child. Why?
But the parent child visualisation is part of Checkmk and if I understand correctly being developed actively, so I do not understand why all the bugs are not fixed. There seems to be more development of fancy layout than fixes to very basic problems.
It seems very unstable with very odd behavior. Hosts snap back when topology is saved, some links show others do not, there is no way to collapse parts of the network from the standard view, it does not seem to handle large numbers of hosts well, and functions to stop growing, change topology for a host children, and a collection of other features do not work. Deleting config and starting again helps temporarily but then problems rise again.
So I wonder if anyone has found solutions, or knows if there is work underway to make it more stable.
The topology engine is both powerful and attractive, but as it is now it is not very useful. If generating topology from the monitor menu is a bad idea and it is better to start from a host, then I think the items should be removed from the maintenance menu.
@arvid I guess this is not about my NVDCT and the Network visualization but about the built-in Parent/Child topology. In this case I can not help here… sorry.
I understand but thanks for popping in to confirm.
It would be nice to use your NVDCT with our client as I think it is exactly what they need, but this will have to wait until I have time to look at it in more detail.
Meanwhile, I am stuck with parent/child and need to present it to my client. It would be nice to be able to say that the flaws in the current implementation are fixed in newer releases, or that they are being worked on, or that the Checkmk development team are looking at the issues, or at least that Checkmk are aware of the issues.
Without a roadmap the whole nagvis parent/child thing feels too much like something that was accidentally included in Checkmk.
Perhaps there is a roadmap that I have overlooked? Or a set of fixes in recent releases? Has anyone seen one?