Skip to main content

Snipe-IT

Visualizes Snipe-IT information, map Snipe-IT users to hardware, and monitors changes through queries and alerts.

Installation​

info

You will need to create a read-access Snipe-IT API key for this integration. See their documentation for more information on obtaining your key for use with JupiterOne.

Configuration in JupiterOne​

To install the Snipe-IT integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select Snipe-IT. Click New Instance to begin configuring your integration.

Creating an instance requires the following:

  • The Account Name used to identify the Snipe-IT account in JupiterOne. Ingested entities will have this value stored in tag.AccountName when the AccountName toggle is enabled.

  • Description to assist in identifying the integration instance, if desired.

  • Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as DISABLED and manually execute the integration.

  • Your Snipe-IT Hostname and API Token (configured for read access).

  • Hardware Category IDs to Filter By, if you only want hardware in specific categories. The IDs are checked when you save, so the Snipe-IT user that owns the token also needs the View permission on Categories.

  • Custom Fields to Include, if you want Snipe-IT custom fields on the Hardware entities. Don't list encrypted custom fields: Snipe-IT returns them decrypted, so their values would be stored on the entity.

Permissions​

The Snipe-IT user that owns the API token always needs the View permission on Users and on Locations. Each data source below also needs its own permission:

  • Hardware: View on Assets
  • Consumables: View on Consumables
  • Licenses: View on Licenses and on Assets

Data sources​

Under Data Sources in the instance configuration you can turn off the resource types you don't want to ingest, for example when your token doesn't have access to them. All of them are on by default.

  • Consumables covers consumables and the users they are checked out to.
  • Licenses covers licenses installed on hardware assets.
  • Turning off Hardware also turns off Licenses, because licenses are collected per hardware asset.
  • Users can't be turned off, because hardware is linked to the users it is assigned to.

Click Create once all values are provided to finalize the integration.

Next steps​

Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.