In a previous post I was playing around with monitoring solutions. Loki and Grafana for log aggregation and dashboards, paired with Nagios (technically Naemon, a Nagios fork, with a web frontend) for host and service monitoring.
After a painful few days of editing Linux config files over and over, make a host, make a service, make a host group, make a service group, figure out what to monitor, figure out how to monitor it, rinse and repeat. I got it working. Technically. It was technically monitoring my 60-odd network devices. It was also technically taking me forever.
I knew I needed some kind of database or inventory system to keep all of this organized. I was actually thinking about building my own, figuring out the schema, the relationships, all of it from scratch. Because that’s what I do. I build things.
Then I stumbled across NetBox.
I think I first saw it on NetworkChuck’s channel. He mentioned it in passing, and I went down a deep rabbit hole. Turns out what I’d been missing in my career wasn’t NetBox specifically, it was DCIM in general.
DCIM: Data Center Infrastructure Management. I knew the concept without knowing the acronym. I’d been doing this kind of work, tracking devices, documenting infrastructure, mapping relationships between systems,for years. I just never had a name for the discipline.
For context: NetBox sits in a different category than the monitoring tools I was already using. Tools like Nagios, PRTG, or WhatsUp Gold tell you whether something is up or down. NetBox tells you what you have and where it is. It’s an inventory and source of truth, not a monitoring platform. They complement each other, monitoring needs to know what exists before it can tell you if it’s working.
Other tools in the DCIM/asset management space include Nautobot (a NetBox fork), Device42 (commercial), Ralph, and Snipe-IT. I can’t say I’ve done deep research across all of them. But NetBox is open source, well-documented, and, here’s the line that hooked me,it was built API-first.
That means if I can figure out how to get the data into it, I can pull it out any way I want and reuse it everywhere. One source of truth feeding monitoring, automation, documentation, and whatever else I build next.
I watched a one-hour NetBox training to get the basics down. I’m about a week in. And it’s already changing the way I organize my infrastructure. It’s starting to open my eyes to what’s possible once everything is documented and structured.
Stay tuned. There are going to be a lot of follow-ups on this one. NetBox is turning out to be the linchpin I never knew I needed.