Just a comment from a smaller user who has moved away from netbox and realistically went back to spreadsheets. Please don't see it as a negative, netbox may purely just be the wrong product for us.
Some background on our usecase, tldr at the bottom. We effectively just need basic documentation.
Which port on which patchpanel does this drop go to?
Which network port is that connected to?
What vlan should be assigned to it?
Which router manages that vlan?
What network range is on that vlan if any?
What IP address should this device be assigned?
I've always found it just a bit difficult to setup things correctly, partly because everything feels slow. To put it into perspective, I was eventually running netbox on a VPS with 2 Genoa cores and 4 gigs of ram and even then some queries would be slow and page loads felt sluggish. Ping to the DC is sub 1ms on that. To need to provide that much horsepower for a DB with an interface just seemed like overkill to management.
Our usecase was great in earlier versions of netbox, the worst performance degradation came around when the graphql API got pushed and newer versions haven't improved it.
As I said, don't take it as a negative, netbox is a good product and to be fair I have never submitted an issue for this nor have I made an attempt to dig into the code to fix it (you can happily blame Django for that). Internally we see netbox as something we probably didn't put enough effort into doing correctly but at the same time the performance issues are a dealbreaker.
Some background on our usecase, tldr at the bottom. We effectively just need basic documentation. Which port on which patchpanel does this drop go to? Which network port is that connected to? What vlan should be assigned to it? Which router manages that vlan? What network range is on that vlan if any? What IP address should this device be assigned?
I've always found it just a bit difficult to setup things correctly, partly because everything feels slow. To put it into perspective, I was eventually running netbox on a VPS with 2 Genoa cores and 4 gigs of ram and even then some queries would be slow and page loads felt sluggish. Ping to the DC is sub 1ms on that. To need to provide that much horsepower for a DB with an interface just seemed like overkill to management.
Our usecase was great in earlier versions of netbox, the worst performance degradation came around when the graphql API got pushed and newer versions haven't improved it.
As I said, don't take it as a negative, netbox is a good product and to be fair I have never submitted an issue for this nor have I made an attempt to dig into the code to fix it (you can happily blame Django for that). Internally we see netbox as something we probably didn't put enough effort into doing correctly but at the same time the performance issues are a dealbreaker.