TrueNAS
Reads GET /api/v2.0/system/info.
targets: - id: truenas-main product: truenas address: https://truenas.example.com credentials: truenas-keyAuthentication — required
Section titled “Authentication — required”Confirmed live against a real TrueNAS 25.10.7 host: this endpoint
answers 401 without credentials. An API key works as a plain bearer
token:
credentials: truenas-key: kind: bearer value: "${TRUENAS_API_KEY}"Not an SSH probe, despite being an appliance OS
Section titled “Not an SSH probe, despite being an appliance OS”An earlier version of this probe read /etc/version over SSH instead
(TrueNAS’s own /etc/os-release reports the underlying Debian base, not
TrueNAS itself — the same identity-file gap
Astra Linux has). Once a real
API target became available to verify against, the HTTP version
replaced the SSH one outright — enodia has no per-product
dual-transport fallback, so the simpler, better-fitting shape wins
rather than the two coexisting.
Recorded fields
Section titled “Recorded fields”Only version — this probe records no extra fields.
Lifecycle resolver
Section titled “Lifecycle resolver”endoflife:truenas.