Store apps / Fleet connector
Early accessEmetrix CMDB Connector for Fleet
Built to bring device and software inventory from Fleet (FleetDM) into the ServiceNow CMDB, with every write going through ServiceNow's Identification and Reconciliation Engine.
- Status
- Version 1.0, with early access open to ServiceNow teams that run Fleet.
- Works with
- Fleet 4.70 and later, on Fleet Free or Premium.
- Fleet access
- A read-only API user. The connector never changes anything in Fleet.
- Support
- By email. See Emetrix support.
How does Fleet device data get into the ServiceNow CMDB?
The connector reads Fleet through its REST API with a read-only API user and never changes anything in Fleet. The mapping is built in IntegrationHub ETL, so your ServiceNow team can see and adjust it, and every CMDB write goes through ServiceNow's Identification and Reconciliation Engine.
The decisions behind this, in plain language: Bringing Fleet device data into the ServiceNow CMDB
How the data flows
Who it is for
ServiceNow teams that run Fleet or Fleet MDM and need device and software inventory in the CMDB that they can trust and show as evidence, in audits and asset reviews.
What it brings into ServiceNow
Version 1.0 is built to bring in:
- Devices from Fleet as CMDB configuration items: macOS, Windows and Linux computers and servers, with model, manufacturer, operating system, CPU, memory and disk. iOS, iPadOS and Android devices can be included as well.
- Serial numbers recorded with their type, so ServiceNow's identification rules can match devices to records from other sources.
- Every network adapter and its IP addresses, related to the device.
- Storage devices, file systems and, where the device reports them, memory modules.
- Certificates installed on the device (needs Fleet MDM).
- Installed software: into Software Asset Management install records when SAM is in use, otherwise into software instances, with the publisher filled in from Fleet's software catalog where available.
- The device's assigned user, matched to an existing ServiceNow user. It never creates users.
- Running processes, optional and off by default, limited to a list of process names.
Where Fleet data lands in ServiceNow
Version 1.0 is built to land Fleet data as follows.
| What comes from Fleet | Where it lands in ServiceNow |
|---|---|
| Devices: macOS, Windows and Linux computers and servers, with model, manufacturer, operating system, CPU, memory and disk. iOS, iPadOS and Android devices can be included as well. | CMDB configuration items. |
| Serial numbers. | Recorded with their type, so ServiceNow's identification rules can match devices to records from other sources. |
| Network adapters and their IP addresses. | Related to the device. |
| Installed software, with the publisher from Fleet's software catalog where available. | Software Asset Management install records when SAM is in use, otherwise software instances. |
| The device's assigned user. | Matched to an existing ServiceNow user. The connector never creates users. |
Also in scope for version 1.0: storage devices, file systems and, where the device reports them, memory modules; certificates installed on the device (needs Fleet MDM); and running processes, optional and off by default, limited to a list of process names.
What it does and does not do
It does
- Read Fleet through its REST API with a read-only API user.
- Send every CMDB write through ServiceNow's Identification and Reconciliation Engine.
- Build the mapping in IntegrationHub ETL, so your ServiceNow team can see and adjust it.
- Mark devices that stop reporting as stale.
- Match the device's assigned user to an existing ServiceNow user.
- Log every run with its counts.
It does not
- Change anything in Fleet.
- Delete a CI. Retirement is opt-in.
- Create users in ServiceNow.
- Record a software install date. Fleet's API does not return one, so the connector leaves it blank rather than guessing.
- Collect running processes unless you switch that on, and then only those on a list of process names.
How it works
- Reads Fleet through its REST API with a read-only API user.
- Every CMDB write goes through ServiceNow's Identification and Reconciliation Engine.
- The mapping is built in IntegrationHub ETL, so your ServiceNow team can see and adjust it.
- Ships recommended reconciliation rules and its own discovery source.
- An in-app Setup wizard tests the connection and walks through scope, rules and schedules. Every run is logged with its counts.
- Scheduled full and change-only (delta) imports.
Straight answers
Does the connector change anything in Fleet?
No. It reads Fleet through its REST API with a read-only API user and never changes anything in Fleet.
Which versions of Fleet does it work with?
Fleet 4.70 and later, on Fleet Free or Premium.
Can it run alongside SCCM, Intune or Jamf?
Yes. It ships recommended reconciliation rules and its own discovery source, and every CMDB write goes through the Identification and Reconciliation Engine, so it can run alongside other sources such as SCCM, Intune, Jamf and Fleet's own sync without fighting them.
Does it delete CIs when a device stops reporting?
No. Devices that stop reporting are marked stale. The connector never deletes a CI, and retirement is opt-in.
Does it create users in ServiceNow?
No. It matches the device's assigned user to an existing ServiceNow user and never creates users.
Can our ServiceNow team change the mapping?
Yes. The mapping is built in IntegrationHub ETL, so your ServiceNow team can see and adjust it.
Does it record software install dates?
No. Fleet's API does not return a software install date, so the connector leaves it blank rather than guessing.
How reliable is the last-used date?
It comes from Fleet's last-opened date. It is reliable on macOS and indicative on Windows and Linux.
Does our Fleet administrator need to add anything?
Yes, for some data. Network adapters beyond the primary one, storage, file systems, memory modules and processes come from a small set of Fleet reports that Emetrix provides for your Fleet administrator to add.
Early access
Name, work email and company; the Fleet connector is already selected. We use it to contact you about early access, and nothing else.
Fleet is a trademark of Fleet Device Management Inc. Emetrix is not affiliated with Fleet.