Documentation of processes, systems, settings. Dependency map. What can be done?

Question

Documentation

Greetings.
Now I am engaged in a complete reorganization of the IT infrastructure in the company
, I immediately want to document everything, but so far, apart from MS Visio, I see no options for how to describe multiple dependencies of systems and networks.
For example:
There is a domain controller, it is a virtual machine, so it depends on such and such a hypervisor 1.
Hypervisor one depends on oops 1, which depends on input 1 and oops 2, which depends on input 2.
there is a file server that lives on hypervisor 2 and depends on it and on basket 1, which is connected to it through switch 1 (ups 3), which depends on ups 3 (input 2) and so on and so forth throughout the network.

In the direction of which names or classes of software to google, if there is a ready one?

It’s clear from monitoring that the same nagios learned how to build dependencies a few years ago - if such and such a switch lies, then such and such services are not available and it makes no sense to squeak at an accident on them. (Zabbix, but it also seems to be able to)

PS - I did not find a hub about documentation, so I considered inserting it into three three hubs

Thanks for the hint and help.

Answer 1

www.lucidchart.com/www.gliffy.com/
_

Answer 2

everything is complicated here - just such a task in full growth
nagios is somehow dull, although I didn’t get into it much, maybe I just don’t know, but the map is built at once. Tasks more complicated than a stupid dependency, such as the availability of a node from two links or vlan through an external provider, cause me mixed feelings so far.
zabbix is ​​better, but the triggers are kind of monstrous in complex cases. The map is pretty and what's good, you can tie it to the area and set all sorts of goodies. I like how access is divided - divided into groups and everyone gets the necessary information.
I would like to improve both systems and zabbix in this regard looks better to me personally. At least I was able to set up the agent for services as it suits me. I collected the necessary data for optimization, the inventory went perfectly, and so on.
According to the documentation, I just stuck mediawiki and fasten jsplumb to it to show diagrams and type schemes like in visio. I hope to get by with this.
I divided the information in zabbix which can and should be monitored and in the wiki which needs to be documented.
The plans are to tie one to the other and tie end devices from the asterisk and the network to all this to receive SLA reports and technical support support and so on.
PS. then there are already three hub hubs :)