ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #netbox
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 exposes its REST API through Django REST Framework, and the DjangoFilterBackend permits double-underscore traversal into related model fields. When building client queries that filter on attributes of related objects, the exact set of supported lookup expressions—such as exact, containment, or range lookups—can be difficult to predict without inspecti
Background NetBox v3.5+ uses RQ workers to deliver webhook payloads with a configurable WEBHOOK_TIMEOUT (default 10 seconds) for the outbound HTTP request. The same worker process honors RQ_JOB_TIMEOUT (default 300 seconds) as a hard limit on job execution time. Observed gap When a remote endpoint exceeds WEBHOOK_TIMEOUT , the HTTP client aborts and marks th
Goal Prevent intermittent database connection pool exhaustion in a NetBox deployment serving variable API traffic, webhook bursts, and scheduled housekeeping jobs. Constraint PostgreSQL max_connections is fixed (e.g., 100–200). Each Gunicorn worker, RQ worker, and runhousekeeping invocation holds a dedicated connection when DATABASE_CONN_MAX_AGE > 0. Unde
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
NetBox records model changes in its built-in change log, and administrators may want to use that history to reconstruct a pre-migration state after a schema change. The uncertainty is whether this log remains a reliable rollback source when a Django migration is reversed, especially on instances where plugins have extended core models or added custom fields.
I'm planning a NetBox deployment for a low-traffic internal workload and want to keep infrastructure cost minimal. Since NetBox is open-source, the real cost driver is its documented stack: the Django application plus one PostgreSQL database and one Redis instance. I'm trying to decide how far I can consolidate that footprint without breaking supported behav
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
postgresql
redis
django