Prometheus Exporter

Feature Requests
1

Problem/Justification
Prometheus and Grafana are well know monitoring system. Now we do add an converter and mapper to scrape metrics for prometheus.

Impact
A user who want scrape truenas metrics can do it easily.

Advantage : no need to put converter somewhere for scrape metrics.
Disadvantage : truenas team must code it

User Story

  1. the user choice metrics in a check-tree for scrapping
  2. the user choice which IP can scrape this metrics
  3. the user enable it and finnish
2

can prometheus ingest data from graphite? If yes truenas can already add a graphite exporter. Another option would be intsead of prometheus to use the graphite exporter to influxdb and then to grafana.

3

The real problem right now is that the system provides too few metric data points—many indicators are missing.

4

A graphite exporter mapping file for truenas scale >23.10.1 metrics and some example grafana dashboards

Going forward from exporter configuration version 2.1, you must also use the Netdata configuration included in the repository to restore the pre‑25.04 metrics. Instructions are provided below. This action is taken since TrueNAS 25.04 dropped a lot of default metrics which doesn’t make sense for me.

5

No, you need a converter graphite to prometheus.
Something like that : GitHub - prometheus/graphite_exporter: Server that accepts metrics via the Graphite protocol and exports them as Prometheus metrics

6

You have right, very few data points.

But I have see in /etc/netdata/netdata.conf, you can enable more metrics.
I don’t understand why they have not implemented this netdata plugin : ZFS Pools | Learn Netdata.

Yes, I have see and test the work to suppoterino.
But do you think it is normal to do all this stuff for only scrape metrics ?

why in something like octoprint, 2 click and it is finnish ?
A 3D printer software (Octoprint) is more monitor friendly than a NAS pro software (TrueNAS), why ?

7

It seems to be due to licensing issues? Although I don’t know why netdata had to be chosen in the first place, and then some things started being removed because of other problems

8

where have you see the licensing problem ?

But I think a serious software pro need metrics to be monitored.

9

A quick and dirty way to have prometheus metrics :

  1. on truenas go to /etc/netdata/netdata.conf and replace “127.0.0.1” by “0.0.0.0” or IP of your monitoring system. restart netdata service.
  2. check with internet browser http://TruenasIP:6999/api/v1/allmetrics?format=prometheus&types=yes&help=yes&timestamps=no