netbox

Use https://github.com/digitalocean/netbox to record your network information. Then you can create topology maps with dot/graphviz. https://netbox.readthedocs.io/en/latest/additional-features/... Someone has a tutorial on using graphviz directly: https://mikegriffin.ie/blog/20110308-a-graphviz-tutorial

We use Racktables [0] (currently migrating to Netbox [1]) and a naming scheme like $product-$environment$servertype-$optDetails0[1..n] with a well known set of abbreviations. So if I need to check the production nameserver it's ns-pdap-01.internal.tld and so on. [0] https://www.racktables.org/ [1] https://github.com/digitalocean/netbox

It might be helpful if described your infrastructure. There is a pretty big difference between managing physical Windows servers in a data center and managing Linux servers all in AWS. If you are all or mostly cloud, Terraform + config management with a CI pipeline takes care of a lot. Then a wiki that covers "Getting Started" and a few how-to articles. For physical infra you need the setup for DHCP, updating DNS based on DHCP, PXE boot imaging, IPMI access and configuration, switch and router configuration, what servers are connected to which switch ports, PDU management and monitoring, and on and on and on. You end up with something like NetBox (https://github.com/digitalocean/netbox) or Collins (https://tumblr.github.io/collins/), plus a bunch of other stuff gluing things together.

- keep inventory in a DCIM (we use Netbox) - configure everything as code (we use Ansible for the infrastructure up to OS level, Kubernetes w/ Helm for applications), have it read the values from the DCIM so that the DCIM remains the single source of truth (we need to still get better on this part....) Links: https://github.com/digitalocean/netbox https://www.ansible.com https://www.kubernetes.io That's at work. At home, I do much of the same, except that maintaining a DCIM is excessive for 2 VPS and a home network of 3 boxes.