Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

A source of truth should only be changed based on a deliberate controlled action. Your VM shouldn’t be changing IPs, if “somebody” changes it you have a chaotic network and you just want a network discovery tool.

The change to the VM’s IP should be done through an auditable change process (like a pull request). If the VM doesn’t match the source of truth, the VM is wrong, not the source of truth.

That PR process would also update your telegraf plugins to ensure that the new IP is being monitored etc.

Net is won’t change the process, your automation (an ansible playbook perhaps) would do the change based on the information in the source of truth

Now it’s possible you only have a couple dozen hosts and a handful of networks and thus your source of truth could be an inventory file, that’s a reasonable solution. When you have dozens or hundreds of switches and hosts in the thousands or more range, I would prefer to have a UI wrapped around that file though, with various links between different locations, switch ports, MDU outputs, etc, that’s where netbox comes in. Your grafana dashboard can take the physical location and tie in with your various monitoring (host and environment) to identify a problem in a specific part of your data centre quickly and reliably, as netbix knows what rack the host is in, what switch it’s connected to, etc



Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: