Integrate with Homebox inventory (inventory.lotusguild.org) for asset linking #27

New Issue

2026-08-31T21:39:18-04:00

jared commented

2026-08-31 21:39:18 -04:00

Type: Feature request

Integrate hwmonDaemon with the self-hosted Homebox inventory instance at https://inventory.lotusguild.org/ so hardware/health alerts can be linked to the corresponding physical asset record.

Motivation: hwmonDaemon currently creates tickets in tinker_tickets for hardware/health issues (SMART failures, Ceph health, etc.) keyed by hostname/device, but there's no link back to the asset's inventory record (warranty info, physical location, purchase date, serial number, etc.) that's tracked in Homebox. Surfacing that context alongside an alert would speed up triage (e.g. "is this drive still under warranty" without leaving the ticket).

Possible approach:

Look up the affected host/device against the Homebox API (Homebox exposes a REST API) by hostname or asset tag to resolve an item ID.
Include a link to the matching Homebox item in the ticket description/comment when a ticket is created or escalated (similar to how ticket links already use APP_DOMAIN to build clickable URLs).
If no matching asset is found, degrade gracefully (skip the link, don't fail ticket creation).

Open questions:

How are hosts/devices currently identified in Homebox (asset tag, hostname field, custom field)? Will need a reliable lookup key shared between the two systems.
Auth: Homebox API token storage/rotation, similar to how the existing TICKET_API_KEY is managed in /etc/hwmonDaemon/.env.

**Type:** Feature request Integrate hwmonDaemon with the self-hosted Homebox inventory instance at https://inventory.lotusguild.org/ so hardware/health alerts can be linked to the corresponding physical asset record. **Motivation:** hwmonDaemon currently creates tickets in tinker_tickets for hardware/health issues (SMART failures, Ceph health, etc.) keyed by hostname/device, but there's no link back to the asset's inventory record (warranty info, physical location, purchase date, serial number, etc.) that's tracked in Homebox. Surfacing that context alongside an alert would speed up triage (e.g. "is this drive still under warranty" without leaving the ticket). **Possible approach:** - Look up the affected host/device against the Homebox API (Homebox exposes a REST API) by hostname or asset tag to resolve an item ID. - Include a link to the matching Homebox item in the ticket description/comment when a ticket is created or escalated (similar to how ticket links already use `APP_DOMAIN` to build clickable URLs). - If no matching asset is found, degrade gracefully (skip the link, don't fail ticket creation). **Open questions:** - How are hosts/devices currently identified in Homebox (asset tag, hostname field, custom field)? Will need a reliable lookup key shared between the two systems. - Auth: Homebox API token storage/rotation, similar to how the existing `TICKET_API_KEY` is managed in `/etc/hwmonDaemon/.env`.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: LotusGuild/hwmonDaemon#27