docs/release-notes/version-2.4.md
peer_device and peer_interface on API /dcim/connected-device/ endpoint to use underscores?brief=1DoesNotExist exception when deleting a device with connected interfacesWebhooks enable NetBox to send a representation of an object every time one is created, updated, or deleted. Webhooks are sent from NetBox to external services via HTTP, and can be limited by object type. Services which receive a webhook can act on the data provided by NetBox to automate other tasks.
Special thanks to John Anderson for doing the heavy lifting for this feature!
Tags are free-form labels which can be assigned to a variety of objects in NetBox. Tags can be used to categorize and filter objects in addition to built-in and custom fields. Objects to which tags apply now include a tags field in the API.
Sometimes it is desirable to associate arbitrary data with a group of devices to aid in their configuration. (For example, you might want to associate a set of syslog servers for all devices at a particular site.) Context data enables the association of arbitrary data (expressed in JSON format) to devices and virtual machines grouped by region, site, role, platform, and/or tenancy. Context data is arranged hierarchically, so that data with a higher weight can be entered to override more general lower-weight data. Multiple instances of data are automatically merged by NetBox to present a single dictionary for each object.
When an object is created, updated, or deleted, NetBox now automatically records a serialized representation of that object (similar to how it appears in the REST API) as well the event time and user account associated with the change.
latitude and longitude fields to Site for GPS coordinatescreated and last_updated fields to DeviceType/extras/config-contexts/, /extras/object-changes/, and /extras/tags/ API endpointscreated and last_updated fieldslatitude and longitude fieldsnapalm_args field