v4.0.8.1

This is a major release and includes bug fixes, new features and improved documentation.

The as tested Netbox version is 4.0.8.

Fixes

• Fixed device_role on devices as the Netbox v4.x source is now the same as virtual machines, role, the exported var is still device_role to maintain backwards compatibility for existing configuration. This release won't work with older version of Netbox.

New Features/Improvements

• Add convenience field primary_oob_address which is the primary ip address of out of band addresses on devices and virtual machines.
• #44 Add a Import for custom field choices which returns a row for each extra choice in a given custom field choices.
• #42 Add a checkbox so devices and virtual machines can import linked interfaces as a list or, with custom fields, dictionary per host.
• #42 Improve the Services checkbox to allow more control over what services are imported and allow the importing of service dictionaries.
• #42 Add new checkbox Parse all data for list columns which make the director internal call listcolumns() return all rows instead of the first row (default). This was required for linked Services and any query where the first row returned doesn't already contain all possible columns. This can increase the API load to Netbox dramatically.
• #39 Add director import baskets to doc/baskets as a starting point for setting up the automation infrastructure. These are intended to be a shortcut/example for setting up your own monitoring.

Readme

• #42 Add/improve info on linked Services, Interfaces and Contacts
• #39 Add info on basket usage as well as the methods the baskets use.
• Update Best Practices.

v3.6.1.3

Improvement

Adds new fields icinga_service_type and icinga_var_type which return the object type from icinga_service and icinga_var so you can safely use filters to solve issues raised in #34 and #35.
Updated Readme with usage.

v3.6.1.2

Minor Release

• Add IPv4 and IPv6 ip addresses alongside primary IP address. Note Netbox makes the primary ip the IPv6 address if it is set
• Add region keyid for region on site
• Add tenant group keyid for parent on tenant

v3.6.1.1

Minor Fix Release

Fix missing string cast causing deprecated explode call (#31)
Fix missing version bump

v3.6.1.0

Note the jump in version just means I haven't tested it on older versions of Netbox, it will likely still work on recent versions of before 3.6.x.

Support for PHP8.2

Fixed #26 : Add fix to remove warnings in PHP 8.2

Add Racks as Import Source

Racks is now a option as a import source.

Racks can have duplicate names in Netbox which isn't allowed in Import Sources. If you have duplicate remove the duplicates in Netbox, and add custom validation, or use the munge option to create unique values.
eg: Munge: keyid,id and Key Column Name: keyid_id

v3.1.16.9

Linked Services

Added checkbox for linking Services to Devices and Virtual Machine. This changes the default behavior for linked objects services to NOT link, this breaks existing installations that use linked services and requires the new option to be checked in import sources to maintain existing functionality.

The choice to break backwards combability has been made because a) not linking is the better default and probably not needed for a portion of imports already, b) broken imports that rely on services should fail in a noticeable way on upgrade and c) be easy to fix by checking the new option Link Services.

Contact Assignment

Contacts assignments are how Netbox links Contacts objects with other Object in Netbox. This release allows you to import contact assignments into director as well as automatically links contacts to devices and virtual machines.
There may be additional Netbox object types that link to contacts, eg: sites, create an issue or contribute the changes yourself if you will use this functionality.

As with linking services above a checkbox has been add for linking Contact Assignments (https://netbox.example.com/api/tenancy/contact-assignments/) to Devices and Virtual Machine

v3.1.16.8

Bug fix release: Default Linked Column Values

Director will make a query through Netbox Import Module to build column headings, the Netbox Import Module is setup to return one result for any object to improve efficiency, query?limit=1.

The bug fixes in this version aim to ensure columns exist for linked objects with a NULL value if the single imported row doesn't contain any links.

This means the type_map of each object will need to be maintained with all linked object names across Netbox versions.

v3.1.16.7

Bug fix release

• a79930b Fix error with icinga_host convivence vars reading the satellite values instead of host values.
• 2bd0df8 Fix error with munge option on devices and virtual machines what also have services.

Note: 2bd0df8 also prevents the flattening of service or range objects, this is by design.

v3.1.16.6

Release Notes

FHRP Groups

FHRP Groups are a good way to store VIP's in Netbox. 2 new import type have been created for FHRP Group.

FHRP Groups

This imports the FHRP groups as they appear in Netbox with a few convivence fields like ip_addresses_array.

FHRP Groups Split (on IP)

This import FHRP Groups and splits the group on IP address, 1 row per IP. The description field modified for each row to be a concatenation of description + primary_ip_address to allow for the creation of unique descriptive host object names.
There are convivence fields and linked zones in this mode.

Bug fix when importing data that is a potential keyid and a null value

KeyID's are created automatically. Some devices, and possibly other objects, can have NULL values for the fields that keyid is generated from.
A fix has been added in this release to make keyid's from fields with a NULL value return a NULL value. This ensures all rows and columns are created in import source.

v3.1.16.5

Add Netbox IP Range Objects

The Icingaweb2 Netbox Import module automatically links the Netbox IP Range Object to Devices and Virtual Machines using the Primary IP address.

Add Automatic import of icinga_zone custom field from IP Range objects to Devices and Virtual Machines.

Adding a custom field icinga_zone to a IP Range will pull the listed value to Devices and Virtual Machines. This makes it very easy to specify that all IP's in a given range belong in a given zone.

_If you add custom field for Endpoint and Endpoint FQDN then other tools, like a ansible satellite deployment role could use the same linking to pull all data required for satellite deployment directly from Netbox.