Collector Reference: IT Asset Management

The Snipe-IT collector discovers IT asset inventory from Snipe-IT, an open-source IT Asset Management (ITAM) platform. It provides the financial source of truth for hardware purchase costs, depreciation schedules, software licenses, and maintenance contracts.

---

Snipe-IT Collector

The Snipe-IT collector connects to the Snipe-IT REST API and discovers hardware assets, software licenses, and maintenance contracts. It handles Snipe-IT's nested API structures (flattening model, manufacturer, category, and status objects), resolves depreciation schedules from separate API lookups, and normalizes financial fields.

CI Types Discovered (3)

Authentication

• Snipe-IT API Token: Personal API token generated in Snipe-IT (Settings > API). Requires read access to hardware, licenses, and maintenances endpoints.
• Token is passed as Authorization: Bearer <token> header.

What Gets Collected

Hardware Assets:

• Config (tracked): Asset tag, serial number, model, manufacturer, category, status, purchase cost, purchase date, order number, warranty months/expiration, depreciation schedule, supplier, location, assigned user, custom fields
• Metrics (not tracked): Checkout counter, checkin counter, last audit date

Licenses:

• Config (tracked): License name, product key, seat count, category, manufacturer, purchase cost, purchase date, expiration date
• Metrics (not tracked): Free seats count, checkout count

Maintenance Contracts:

• Config (tracked): Title, cost, start/completion dates, warranty flag, maintenance type, supplier, associated asset name

Key Relationships

• Maintenance contracts depends_on Hardware assets (matched by asset name)

How Snipe-IT Feeds Cost

Snipe-IT hardware purchase costs are a capital cost source for cost calculation. License and maintenance-contract costs are collected and tracked in change history, but they do not enter the cost model.

• Amortisation window. An asset charges its purchase cost divided by its depreciation months, starting at its purchase date and lasting that many calendar months. The months come from the asset's Snipe-IT depreciation schedule; an asset without one uses the default depreciation period, 36 months unless your deployment sets another. After the window the asset charges 0.
• Missing purchase date. An asset with a purchase cost but no usable purchase date is amortised with no end date and flagged on the Cost Explorer's Quality tab. Add the purchase date in Snipe-IT to bound it.
• Where the cost lands. The asset's cost is placed on one correlated record of the same machine, preferring the record that passes cost on to workloads (for example a Proxmox node), so it reaches the VMs running there. A capital rate card on the same machine is then superseded, including after the asset is fully depreciated.
• Currency. Snipe-IT does not record which currency a purchase cost is in. Parascope assumes Snipe-IT costs are in your tenant's base currency and does not convert them. If your Snipe-IT records use another currency, convert them in Snipe-IT, or price that hardware with capital rate cards instead.

Configuration

Configured via Settings → Collectors when adding a Snipe-IT source.

---

Related Documentation

• Managing Collectors: Collector health and lifecycle
• How cost is calculated: How Snipe-IT purchase costs are amortised and placed
• CI Types: Complete CI type reference