Automating the data center inventory using different channels sometimes results in finding the same device under different names. This often causes device info spread out across multiple devices in the device42 database. We have addressed this issue with introduction of aliases for devices. Now you can merge two or more devices. When you merge, you will choose a master device, and any future auto-discoveries will update the merged master device only. In addition to device aliases, we have also added custom key value pairs for building, room and racks. These changes and some other new additions in v4.3.0 are discussed below.
Easier data center inventory with device aliases
Now you can merge two or more devices using bulk action from Devices > All devices. The device type should for merged devices should be same or unknown. Once you select the devices and click Go, you will see a confirmation screen where you will choose the master device and confirm the merge. IP and MAC address info from the merging devices will then be migrated to the master and all other properties of the non-master merged devices are deleted. From this point forward, any future auto-discoveries will update the master device. You can view any device aliases you’ve created on the first tab in device properties. The Search function will also find the aliases. Last, the device add/update RESTful API now takes aliases as an argument.
Bulk action for changing device type unknown
You can now make bulk changes to the device type unknown using bulk actions from Device > All devices. You can select multiple devices with “unknown” type and assign the chosen type in bulk.
Custom key pair values for building, room and rack
You can now bring your custom keys, values(and value2) for buildings, rooms and racks. The custom key pair values for these objects work similarly to custom key value pairs for devices and customers.
More export options and changes to export
We have added more options under Tools > Export. Now almost all objects are available to be exported as csv files. The default file name now matches the object description name.
History (audit log) via REST API
Retrieving the history log is now available through REST APIs. You can read more at device42 API documentation page for history.
Other REST API enhancements
- Vendor GET API added.
- Hardware add/update REST API added.
- Customer custom contacts REST API added.
- End user add/update REST API added
- Asset types in the filter list and when adding a new asset are now sorted alphabetically.
- vendor name added to API output in assets.
- IE rendering of report menu was broken. Now fixed.
- Switch template was not creating correct # of switches for stacked switches. Now fixed.
- Home page search errored out on non-english alphabets. Now fixed.
- Rack hover was getting cut off in the bottom for longer racks or for blade devices hover overs. Now fixed.