TrueNAS¶
At the end of this page Ferrule will be reading TrueNAS SCALE or CORE: pools, every disk's errors and temperature, and TrueNAS's own alerts.
In TrueNAS¶
- Credentials → Users → Add: a user
telemetrywith the Read-only Admin role. - Create an API key for that user, and copy it now.
In Ferrule¶
- Click Settings ⚙ and find Add a source.
- Kind: TrueNAS. Fill in Name (anything you'll recognise), Address and User (blank for an API key).
- Ferrule writes two lines, such as
SOURCE_1=...andSOURCE_1_SECRET=.... Click Copy. - Add both lines to your settings, and replace the placeholder in the
_SECRETline with the API key:
- Open the
ferrulestack and find Environment variables. - Add or change the lines. In Advanced mode you can paste several at once.
- Click Pull and redeploy.
- Open
.envin the folder where you clonedferrule-deploy. - Add or change the lines.
- Run
docker compose up -din that folder.
Ferrule never asks for the API key
It only goes into your settings. The Settings page shows whether it's set, never what it is.
- Address:
https://<truenas> - User: leave it blank to use the API key.
How to know it worked¶
- Settings → Sources lists it, with the state polling. Right after an update it says waiting for first poll for up to a minute.
- It appears on the Storage tab.
What it alerts on¶
TrueNAS's own alerts, just as TrueNAS shows them. Dismissing an alert in TrueNAS clears it in Ferrule.