client’s architectures. An essential component of managing any environment is proper documentation. We’ve worked towards this goal through a number techniques...
rule them all. We use an extensive configuration manager (mix of Puppet and our own tech). Perusing through a config reveals architecture and layout. We monitor and trend EVERYTHING. One look at the dashboard for a server reveals important services.
stacks, techs, etc...), glancing at a config or monitoring control panel is not enough. Some form of visualization would help greatly. Network diagrams are very helpful.
can inspect and report on active network and socket connections. Reads in data from /proc Lists incoming connections, outgoing connections, listening sockets, ports, IPs, etc...
an architecture - these are the nodes. Log into each server and grab a list of both listening processes, and active connections. For each listening process, find all connections from external servers connecting to it. These are the edges. Output this data to a format of your choosing (.dot file, CSV, etc...).