Device42 is a Continuous Discovery software for your IT Infrastructure. It helps you automatically maintain an up-to-date inventory of your physical, virtual, and cloud servers and containers, network components, software/services/applications, and their inter-relationships and inter-dependencies.
This repository contains script that helps you sync data from Device42 to Freshservice.
Device42 v16.19.00+ (Legacy Included) Python 3.5+
The following Python Packages are required:
- pycrypto==2.6.1
- pyparsing==2.1.10
- pyzmq==16.0.2
- requests==2.13.0
- xmljson==0.2.0
These can all be installed by running pip install -r requirements.txt.
Once installed, the script itself is run by this command: python d42_sd_sync.py.
To utilize the Device42_freshservice_mapping script, Python 3.5+ is required. The following Python Packages are required as well:
pycrypto==2.6.1 pyparsing==2.1.10 pyzmq==16.0.2 requests==2.13.0 xmljson==0.2.0 These can all be installed by running pip install -r requirements.txt.
In order to run the legacy migration, you will also need to modify the mapping.xml file so that the legacy mapping options are used
modify the following line so that enable is set to false for the v2_views
enable="false" description="Copy Servers from Device42 to FreshService using DOQL v2_views"
modify the following line so that enable is set to true for the v1_views
enable="true" description="Copy Servers from Device42 to FreshService using DOQL v1_views"
Once the packages are installed and the script is configured, the script can be run by this command: python d42_sd_sync.py.
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, and default approver email address in the Freshservice and Device42 sections (lines 2-11). 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 section of each task, there will be a 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 section.
Once the Device42 API resource and Freshservice Target are entered, the 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 device 42 (for example, service_level).
After configuring the fields to map as needed, the script should be ready to run.
- Freshservice API Limit is 1000 calls per hour (https://api.freshservice.com/#ratelimit)
- Due to the nature of Freshservice rate limits, large inventories may take extended periods of time to migrate
Please use the following table as a reference only, actual times may vary due to request limit cooldowns and other internal API calls
| # of Devices | Migration Time |
|---|---|
| 100 | 6 min |
| 1,000 | 1 hr |
| 5,000 | 5 hrs |
| 10,000 | 10 hrs |
| 24,000 | 24 hrs |
- Script runs on Linux and Windows
- mapping.xml - file from where we get fields relations between D42 and Freshservice
- devicd42.py - file with integration device42 instance
- freshservice.py - file with integration freshservice instance
- d42_sd_sync.py - initialization and processing file, where we prepare API calls
We will support any issues you run into with the script and help answer any questions you have. Please reach out to us at support@device42.com
2.0.0.201207