Snipe-IT
Connect NetLock RMM to Snipe-IT: assets you keep in Snipe-IT get NetLock fields, Snipe-IT stays your record of what you own.
Snipe-IT
Snipe-IT records what you own, so NetLock does not change that record. It only fills the columns you choose on assets that already exist. Asset tag, name, serial number, model, status, location, assignment and notes stay as they are, and nothing is ever deleted.
Requirements
- Snipe-IT 8 or later. The test of the connection reads the version and refuses an older one.
- A personal access token of an account that may read and edit assets and read companies, models, status labels and custom fields. It is created in your profile under
Manage API Keys. - The address of the instance, without
/api. - Custom fields for the values of NetLock, added to the fieldsets of your models. Their name must contain
NetLock. NetLock does not offer or write any other field, so a field you maintain cannot be overwritten by mistake.
| Suggested name | Content |
|---|---|
NetLock device id | The id of the device in NetLock. Required |
NetLock last seen | The day of the last contact |
NetLock OS | Operating system |
NetLock agent version | Version of the agent |
NetLock URL | Where the device opens in the console, if a public console address is set |
Use plain text fields without encryption. An asset whose model has no field for the device id is skipped with fields_missing.
- Tenants map to companies, which requires
Full Multiple Companies Support. For an instance without companies, see below.
Setup
- In
Settings → Integrations, open the Snipe-IT tile and chooseConnect. - Enter the
Instance addressand theAPI token.Allow unencrypted httpis for an instance on an internal network only. - Under options, choose the field for each value. The lists are read live from Snipe-IT. Only
Field for the device idis required; a field left empty is not written. - Switch on
Sync devices as assets. It is off by default: without it the connection does nothing. - Map each tenant to a company, or import the companies. Tenants without a mapping are not included.
- Activate the connection.
The test of the connection shows the version of Snipe-IT and reports when a field is missing or no company exists. It writes nothing.
Instance without companies
With This instance uses no companies on, the mappings offer one company for all assets, which several tenants can share. Names are then not unique across tenants, so only the serial number and the device id field are used to match a device.
What goes to Snipe-IT
The chosen columns, and only those. A value NetLock does not know is left out. An asset that already holds the same values is not written, so it does not appear in the history of Snipe-IT.
Every hour NetLock checks the devices that changed since the last run. The last contact is stored by day. Synchronize now starts a run immediately.
How a device finds its asset
By exact match, within the mapped company. The first step that finds an asset wins:
- The asset of the stored link. A deleted asset is treated as missing.
- The asset whose device id field holds the id of the device.
- The asset with the same serial number. Placeholders such as
To Be Filled By O.E.M.are ignored. - The asset with the same name.
Steps 3 and 4 ignore case. If the name matches but both sides have a real serial number and the numbers differ, they are two machines and the device is skipped as ambiguous.
A device is skipped, without counting as a failure, when:
| Reason in the history | Meaning |
|---|---|
not_in_source | Snipe-IT has no such asset |
ambiguous | Several assets fit, or the name fits and the serial numbers differ. Make the serial number or name unique, or fill the device id field of the right one |
taken | The one asset that fits belongs to another device. After a reinstallation a machine gets a new device id: clear the device id field of the asset, and the next run links it |
fields_missing | No field for the device id is chosen, or the model of the asset does not have it |
create_incomplete | Creating is on, but a mapping or option for it is missing |
Such a device does not count as a failure and is checked again a day later, or within the hour for fields_missing and create_incomplete. Saving the settings, changing a mapping or Synchronize now ends the wait. An asset that moved to another company, or whose device id field names another device, is no longer written. If no new match is found, the link is removed, so the device no longer shows the asset.
The External systems tab of the device links to its asset.
Creating assets
Create assets that are missing is off by default. With it on, a device without a match becomes a new asset in the mapped company. Creating requires a model for the device class under Mappings and a Status label of new assets. The asset tag is NL-<device id>; with Snipe-IT numbers new assets on, Snipe-IT sets it, which requires automatic asset tags in its settings. The model has to carry the chosen fields, otherwise Snipe-IT refuses the asset.
Known limits
- NetLock treats a refusal by Snipe-IT as a failure of the device and names the fields concerned.
- Snipe-IT allows 120 requests a minute per user by default. NetLock stays below that with one request every 0.55 seconds, so a large first run takes several hourly jobs. A lower limit of your instance is respected when Snipe-IT reports it.
- Data flows in one direction only: Snipe-IT data does not flow into NetLock.
NetBox
Connect NetLock RMM to NetBox: devices and virtual machines you keep in NetBox get NetLock fields, NetBox stays the source of truth.
Wazuh
Connect NetLock RMM to Wazuh: disconnected agents, high level alerts and, if you want, critical vulnerabilities become alerts of the matching device or tenant.