|
|
@@ -4,13 +4,15 @@
|
|
|
|
|
|
A NetBox model represents a discrete object type such as a device or IP address. Each model is defined as a Python class and has its own SQL table. All NetBox data models can be categorized by type.
|
|
|
|
|
|
+The Django [content types](https://docs.djangoproject.com/en/stable/ref/contrib/contenttypes/) framework can be used to reference models within the database. A ContentType instance references a model by its `app_label` and `name`: For example, the Site model is referred to as `dcim.site`. The content type combined with an object's primary key form a globally unique identifier for the object (e.g. `dcim.site:123`).
|
|
|
+
|
|
|
### Features Matrix
|
|
|
|
|
|
* [Change logging](../additional-features/change-logging.md) - Changes to these objects are automatically recorded in the change log
|
|
|
* [Webhooks](../additional-features/webhooks.md) - NetBox is capable of generating outgoing webhooks for these objects
|
|
|
* [Custom fields](../additional-features/custom-fields.md) - These models support the addition of user-defined fields
|
|
|
* [Export templates](../additional-features/export-templates.md) - Users can create custom export templates for these models
|
|
|
-* Tagging - The models can be tagged with user-defined tags
|
|
|
+* [Tagging](../models/extras/tag.md) - The models can be tagged with user-defined tags
|
|
|
* [Journaling](../additional-features/journaling.md) - These models support persistent historical commentary
|
|
|
* Nesting - These models can be nested recursively to create a hierarchy
|
|
|
|
jeremystretch