Creating an extended integration for Fleet assets

Let Oomnitza be your single source of truth!

You'll get complete visibility of your assets information as data from Fleet is automatically transformed into consumable information and actionable insights. 

Fleet Device Management is a lightweight telemetry platform specifically designed for servers and workstations. It offers open-source device management solutions that cater to the needs of IT and security teams dealing with a large number of laptops and servers. The platform supports various operating systems, including macOS, Windows, Linux, and ChromeOS. Additionally, it is compatible with cloud services like AWS, Google Cloud, and Azure, as well as data center environments and containers.

The Fleet DM Asset Load uses the Hosts API. For further information, see Fleet API Documentation: List Hosts.

Connect Oomnitza and Fleet in minutes

Get the information and insights that you need to reduce costs and the time that you spend on administration tasks such as:

• Configurable dashboards and list views of key asset information
• Configurable reports to share information about assets and software with your colleagues and management such as corporate-wide reports that detail the distribution and status of the assets in your environment

• Get the information and insights that you need by creating configurable workflows for:

  • Getting detailed host information, including mobile device management details.
  • Deleting a host

Navigation

Creating the integration

Creating custom mappings

Before you start

Credentials

Before you can create the integration with Oomnitza, you need to have added your Fleet credentials to Oomnitza and set your domain as a global variable. 

Adding your Fleet domain as a global variable

Adding your Fleet credentials to Oomnitza

Retrieving software

If software_id is specified in the Hosts API, some additional information about the software object can be retrieved. Make sure to enable the Software checkbox when running the asset load to retrieve the software object information.

Additional headers

In the Fleet asset integration, there are optional fields:

• Additional Header Attribute: Here, you can enter an additional header attribute. For example, you might specify 'Content-Type' as the attribute.
• Additional Header Value: In this field, enter the value corresponding to the header attribute, such as 'application/json'.

Please note that these fields are optional. By default, their value is set to 'default'. When the default value remains 'default', these additional header attributes and values are ignored and not used in the integration.

Creating the asset integration

Information
When creating the asset integration, check Software to enable the retrieval of the host Software name and version.

1. In Oomnitza, click Configuration> Integrations> Overview.
2. Click Block view
3. Scroll down to the Extended section for asset integrations.
4. Click NEW INTEGRATION.
5. Select the integration in the sidebar.
6. Click ADD.

Integration details overview

More information is provided about the following fields to help you complete the integration:

Installation type

Select Cloud if you want to store credentials in the Oomnitza cloud.

Select Local if you want to store credentials locally. Local extended integrations do not support AWS and OAuth authentication. If you want to sync Oomnitza with vendor applications that require AWS or OAUTH authentication, select Cloud.

Integration preferences

By default, the option Create & Update option is selected. Select this option  when you want to edit records and add new records. If you want to edit records and not add new records, select Update Only. If you only want to add new records, select Create Only.

Integration details

To review or update the integrations details, click Edit .

1. Update the integration name if necessary. 
2. Select an installation type.
3. For integration preferences, select an option.
4. Enter the name of the integration user.

Credential details

If you selected Cloud as the installation type, choose one of the following options:

• Select the credentials that were created for the integration.
• Edit the credentials that were created for the integration.
• Create new credentials

Schedule

By default, data is streamed to Oomnitza once every day.

You can configure the schedule to meet your needs such as changing the interval or changing the time so that the data is streamed when your system isn't busy.

1. Click the Edit .
2. Configure your schedule.
3. Click Update.

Mappings

To map the fields to Oomnitza, click Edit .

You can define rules for your integration by selecting Edit integration on the mapping page. For example, you may only want to run the integration if a certain contact or region exists. See Filtering integration results.  
You can add new fields to your integration by selecting Add new field   on the mapping page. All you need to do is specify the property name. See Creating custom API fields. 

Creating custom mappings

Map Fleet fields to Oomnitza fields to get the asset information that you need. For the field mapping, it is recommended to follow these steps:

1. Click Smart Mapping.
2. Create a custom mapping for the Fleet ID field. To do this, complete these steps:
   1. Click the down arrow on the ID field.
   2. Select Add new Oomnitza assets field.
   3. Change the name of the new field to FleetMDM Host ID.
   4. Click the Unique checkbox. 
   5. Click CREATE. 
3. Map and assign a sync key to a unique field, such as the FleetMDM Host ID.
4. Click UPDATE.

Tracking information for asset loads 

When the integration is run, you can track the name of the credentials that were used and the source of the data. To do this, you map the following fields to Oomnitza:   

• Connect: Credentials
• Connect: FleetDM Sub Domain

Custom mappings

Additional
Build
CPU Brand
CPU Logical Cores
CPU Physical Cores
CPU Subtype
CPU Type
City Name
Code Name
Computer Name
Config TLS Refresh
Connector Sync Time
Country ISO
Created At
Detail Updated At
Display Name
Display Text
Distributed Interval
Failing Policies Count
Hardware Model
Hardware Serial
Hardware Vendor
Hardware Version
Hostname
Id
Label Updated At
Logger TLS period
MDM: Encryption Key Available
MDM: Enrollment Key Available
MDM: Name
MDM: Server URL
Memory
OS Query Version
OS Version
Pack Stats
Platform
Platform Like
Primary IP
Primary MAC
Public IP
Seen Time
Software Updated At
Status
Team ID
Team Name
Total Issues Count
UUID
Up Time
Updated At

Launching the integration

Your integration is in Draft mode until the required mandatory fields are added. When added, click Launch to activate your integration. 

If you selected Cloud as the installation type when creating the integration, see Running an extended integration

If you selected Local as the installation type when creating the integration, see Running an extended integration locally.

Viewing data ingested by Oomnitza

Viewing ingested asset data

For asset integrations, click Hardware. If the asset integration also ingests software data, click Software.

Viewing ingested user data

For user integrations, click People. If you chose the option to ingest User and SaaS user data, click Software > SaaS, click the SaaS app, and then click the Users tab. 

Related Links

• Running an extended integration
• Troubleshooting integrations
• Mapping extended integrations

Unleash the power of Oomnitza

To get valuable actionable insights that help you manage your assets, learn how to:

• Configure dashboards for your users and software
• Configure custom reports about your users and software
• Create workflows to automate tasks

See Getting started for more information.