NeoAnd/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2025-07-14 01:41:22 -06:00
Code Issues Actions 5 Packages Projects Releases Wiki Activity

Remove "Can We Add Custom Fields to More Models?": no longer applicable

Jeremy Stretch 2020-12-16 13:00:44 -05:00
parent df925bd3a5
commit 1d80752352
1 changed files with 0 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
Frequently-Asked-Questions.md

@ -2,7 +2,6 @@
* [Why Does NetBox Require Every IP to Have a Mask?](#why-does-netbox-require-every-ip-to-have-a-mask)
* [Why Can't I Connect a Virtual Circuit to an Interface?](#why-cant-i-connect-a-virtual-circuit-to-an-interface)
* [How Can I Add New Interface Form Factors?](#how-can-i-add-new-interface-form-factors)
* [Can We Add Custom Fields to More Models?](#can-we-add-custom-fields-to-more-models)
* [Why Does NetBox Support Only Image Attachments?](#user-content-why-does-netbox-support-only-image-attachments)
# Why Doesn't NetBox Scan for IPs?
@ -51,12 +50,6 @@ NetBox models only physical circuits, which can be terminated to physical interf
The set of available interface form factors is statically defined in NetBox; users cannot add arbitrary form factors. This is done to remove the potential for creating duplicate or illegitimate form factors that would degrade the data model. If there's a form factor you'd like to see added to NetBox, consider opening a [feature request](https://github.com/digitalocean/netbox/issues) detailing your use case. (However, bear in mind that only actual hardware interface types will be added.)
# Can We Add Custom Fields to More Models?
[Custom fields](http://netbox.readthedocs.io/en/stable/data-model/extras/#custom-fields) allow users to define additional data fields on certain NetBox objects. These can be used to track object attributes which are important to an individual organization, but that wouldn't make sense to implement in the official NetBox database schema. For example, maybe you need to add a `legacy_name` field to the Device model, or `ticket_number` field to an IP address.
NetBox allows custom fields to be added only to primary models. Within the DCIM application, for instance, custom fields can be added only to the Site, Rack, DeviceType, and Device models. They cannot be added to the Region, RackGroup, DeviceRole, or other models which are used primarily for organizational purposes. The relevant distinction is that primary models have dedicated views (e.g. `/dcim/devices/<pk>/` for a device) whereas secondary models do not. Thus, it doesn't make sense to included arbitrary additional data. (Custom fields should not be included in object lists due to the overhead they impose, which is one additional query per field, per object in the list.)
# Why Does NetBox Support Only Image Attachments?
NetBox supports the attachment of images to certain models, namely sites, racks, and devices. This feature was added as a convenience to provide readily-accessible photographic documentation of installations. For instance, a data center technician might opt to upload a close-up photo of a device and its connections to clarify where each named interface resides on the box.