ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #netbox
Learn how to create a child prefix in NetBox via the REST API, fetch the first free IP, and assign it to a device interface, with verification and rollback steps.
NetBox's GraphQL API (v3.0+) lets you fetch device, IP, and VRF data in one request instead of chaining multiple REST calls. This blog shows a concrete query, compares payload sizes, and outlines the operational trade‑offs you need to manage.
Lock device classification in NetBox with custom fields for single-value attributes and tag groups for multi-value labels. A task guide covering prerequisites, creation steps, verification checks and safe enforcement with recovery options.
Stop struggling with duplicate IP addresses. Learn how to use NetBox VRFs to manage overlapping IP spaces for multi-tenant environments and maintain a clean Source of Truth.
Use NetBox custom fields to add operational metadata like change tickets and compliance tags to Device, Prefix and VLAN without plugins, with API exposure and clear trade-offs.
Netbox API token‑based authentication The goal is to confirm that an API token created with only the 'read' scope blocks write‑like operations such as creating a new IP address through the /api/ipam/ip-addresses/ endpoint when testing an integration without production credentials. However, anecdotal reports suggest that certain endpoints may still permit imp
Goal To upgrade a small NetBox instance to a newer release while keeping the application online for clients. Constraints & Uncertainty NetBox automatically applies pending Django migrations during startup. This process acquires schema locks that can block read/write traffic, potentially exposing a brief outage. The documented option to suppress automatic
NetBox IPAM provides two primary methods for populating IP addresses within a defined prefix: manual entry of specific addresses and the Next Available IP automation tool. The goal is to maintain a clean, predictable address space while minimizing administrative overhead during device provisioning. Manual assignment allows for strict architectural placement
Goal: Reduce resource consumption and hosting costs for a NetBox deployment that serves minimal API traffic by lowering the API request throttle rate. Constraint: The API_THROTTLE_RATE setting applies globally to all API endpoints, including the browsable UI and external automation scripts, and only takes effect after a service restart; it does not influence
graphql
django