Device42
About
The Device42 context integration provides enriched asset context to Netography Fusion from the Device42 asset management platform. It connects to the Device42 API to retrieve asset information from the Devices table and then uploads it as Context Labels to the Netography Fusion API.
NetoFuse Modules: Cloud deployment vs. on-prem deployment
This page documents how to add and configure the context integration in the Netography Fusion Portal. This will make a direct connection from the Netography Fusion SaaS in the cloud to the vendor API. If you prefer to deploy the integration within your own environment (on-prem or in your own cloud) with a container or Python package, go to the module documentation in NetoFuse Modules.
Adding a Context Integration
In the Netography Fusion Portal:
- Select Settings at the bottom of the left-hand navigation menu
- Select Context Integrations in the Data Management section.
- Select the Add Integration button.
- Select a context integration from the list provided.
- Follow the configuration steps in the documentation for the context integration you selected.
Configuring
| Field | Required | Description |
|---|---|---|
| URL | Yes | URL to Device42 API |
| Username | Yes | Device42 User Authentication Username, if used instead of Token Authentication |
| Password | Yes | Device42 User Authentication Password, if used instead of Token Authentication |
| IP Fields | Yes | Device42 fields to retrieve via API |
| Fetch Devices | No | If set to true, gathers additional fields from Devices table in Device42 |
| Per Page | No | Number of results per API call (max: 1000) |
Selecting Token Authentication or User Authentication
Token authentication is being added in an upcoming release. If you would like to use token authentication now, please contact Netography Support.
Device42 can use either Token Authentication or User Authentication to connect to the API. Token authentication is the recommended approach for a production deployment.
The Username and Password fields are not required if token authentication is used (and conversely, the Client Key and Client Secret fields are not required if User authentication is used).
Device42 Configuration
If using Token Authentication, follow Device42 instructions to generate a Client Key and Client Secret for a production deployment as documented here: https://api.device42.com/#API_Authentication
Transform
The Advanced section of the context integration contains the Transform field. This field allows you to add, remove, or change the mapping of fields returned by the vendor API to Netography Fusion context labels.
See the Context Transforms documentation section for more instructions on editing this field.
It may be helpful to first configure all the parameters and the transform field with a NetoFuse container on your local system and then copy those fields into the Portal once you have validated that everything is configured properly.
Updated about 2 months ago