@Flox
Thanks for the response.
Understand what you are saying about what is suppose to work and be installed right from the start. However, in the case of your proposed Netdata Rock-on, it is not.
This can be seen by looking at the plug-ins as shown in this link: https://github.com/netdata/netdata/wiki/monitoring-IPMI
if I were to look at just the plug-ins.d directory, I get:
[root@rocknas1 admin]# docker exec -it netdata bash
root@rocknas1:/# ls /usr/libexec/netdata/plugins.d
README.md cgroup-name.sh fping.plugin
alarm-email.sh cgroup-network loopsleepms.sh.inc
alarm-notify.sh cgroup-network-helper.sh node.d.plugin
alarm-test.sh charts.d.dryrun-helper.sh python.d.plugin
apps.plugin charts.d.plugin tc-qos-helper.sh
No where does it show the ipmi.plug-in.
If I were to do the listing, as shown in the link above, I get:
root@rocknas1:/# ls /usr/libexec/netdata/plugins.d/freeimpi.plugin -h
ls: cannot access â/usr/libexec/netdata/plugins.d/freeimpi.pluginâ: No such file or directory
Again, shows that freeipmi.plugin is not installed.
I know that one page says that it is supposed to be there, from the startâŠbut it isnât.
The second link, https://github.com/netdata/netdata/wiki/monitoring-IPMI, says it needs to be complied in, and configured in the netdata.conf file, for it to function.
Again, if I search (browswer ctrl-f) within the netdata.conf file, for plugin:ipmi, I get nada. If I do same search for just plugin:, I get 119 hits. Looking through all the hits, again ipmi is not listed. So once again, I say that something is wrong â either the web page, saying it is suppose to work out of the box, or the freeipmi.plugin has been deconfigured/removed, from the .json file you did a pull request from. Either way, it is not there.
If it is the 1st problem, then maybe the config just needs to be added back into netdata.conf. Or, the plugin needs to be downloaded, and netdata needs to be recompiled with it in, and then submitted, after doing such.
Or, it is a bug that needs to be corrected at the upstream level. In that case, a bug report would need be done. In this case, since it is your proposed Rock-on, I assume you would be the upstream (and in turn, you would have to file the report with your upstream source.)
If I can figure out how to get in and edit the netdata.conf file, in your proposed, and add the config portion as listed in `freeipmi.plugin configurationâ on https://github.com/netdata/netdata/wiki/monitoring-IPMI, then I could determine what the issue is. But, thus far, not able to figure out how to get into the netdate.conf. Just know how to list it, from within the browser.
Also, as for testing the availability of the ipmi functioning, you say you canât test because you do not have the same board as I. I say, that if you run âipmimonitoringâ from the Rockstor shell CLI, and look at the output, you probably will find that fans are already being monitored. If that is the case, you donât have to have the same board as I, and therefore the functionality can be tested.
If ipmimonitoring output does not list fans, then I would say your statement would be correct.
Also, being able to do ipmimonitoring would also show that the required library, libipmimonitoring-dev or libipmimonitoring-devel (freeipmi-devel on RHEL based OS), was already installed (which is the case of Rockstor, out-of-the-box, or, as direct result of installing your proposed netdata app).
I know what I am wanting to do maybe a one off configuration. However, because the case fans have been modified (to get rid of the jet engine noise level, as server/NAS is installed in the home office). However, because of the heat factor from Arizona temps, it is important I keep an eye on memory/cpu temps and fan speeds for the NAS/server appliance, remotely.
As I previously stated, there is a work around for the lack of Netdata fan speed monitoring - e.g. doing the ipmimonitoring command from the NAS CLI - until such time as Netdata obtains the functionality, or I can find another solution (such as a widget for the ipmi fan data).
Once again, thanks for the additional input. Still say your proposed is a viable, and needed, Rock-on, for those not needing the fan speed readout(s).