Sync devices and their inter-relationships discovered by Device42 to Freshservice asset management
Device42’s comprehensive agentless autodiscovery [with optional agents] and remote collectors can be used in any combination to automatically maintain an accurate inventory of your physical, virtual, and cloud servers, containers, network components, software, and services as well as critical inter-relationships and dependencies. Scheduled syncs automatically keep Freshservice CIs up-to-date, or quickly refresh on demand
•See complete details about all CIs across your IT infrastructure when Device42 is synced to Freshservice
•Device42 auto discovery is more comprehensive, discovering not only hardware, software, dependencies, and relationships, but also install paths, license details, certificates, configuration files, warranty information, and more - enhance the breadth of information available in your CMDB
•Enjoy better IPAM – all network and IP address details are automatically synced for enhanced IPAM
•Easily tie IT assets to related service requests, and view all problems associated with a given CI along with CI details
•Integration utilizes Device42’s DOQL query language, providing the ultimate flexibility for selecting CIs to sync to Freshservice
•Plus, leverage any or all of Device42’s built-in DCIM features, like power monitoring and control, visual room and rack layouts, RESTful APIs and webhooks to support automation efforts, and more
The integration can be download directly from the GitHub repository: https://github.com/device42/freshservice.git or use git and execute `git clone https://github.com/device42/freshservice.git`
To utilize the Device42_freshservice_mapping script, Python 3.5+ is required. The following Python Packages are required as well:
These can all be installed by running `pip install -r requirements.txt`.
Prior to using the script, it must be configured to connect to your Device42 instance and your FreshService instance.
* Save a copy of mapping.xml.sample as mapping.xml.
* Enter your URL, User, Password, API Key in the FreshService and Device42 sections (lines 2-10).
API Key can be obtained from FreshService profile page
Below the credential settings, you’ll see a Tasks section.
Multiple Tasks can be setup to synchronize various CIs from Device42 to FreshService.
In the <api> section of each task, there will be a <resource> section that queries Device42 to obtain the desired CIs.
Full documentation of the Device42 API and endpoints is available at https://api.device42.com.
Individual tasks within a mapping.xml file can be enabled or disabled at will by changing the `enable="true"` to `enable="false"` in the <task> section.
Once the Device42 API resource and FreshService Target are entered, the <mapping> section is where fields from Device42 (the `resource` value) can be mapped to fields in FreshService (the `target` value).
It is very important to adjust the list of default values in accordance between freshservice and device42 (for example, service_level).
After configuring the fields to map as needed, the script itself is run by the command: `python d42_sd_sync.py`.