ZIMonSensors restrictions are problematic #374
Description
Our ZIMonSensors.cfg on the node where the prometheus_exporter runs has stanzas like this:
{
name = "GPFSNSDDisk"
period = 0
restrict = "nsdNodes"
},
On the ndsNodes the respective stanza looks like this:
{
name = "GPFSNSDDisk"
period = 1
restrict = "nsdNodes"
},
So the sensor is running on the nsdNodes. But as there's a 0 in config file on the exporter node (that is not a member of nsdNodes) the exporter cannot export the GPFSNSDDisk metrics besides them being collected. If I manually change the 0 to 1 on the exporter it is able to report the values.
So I think the exporter should be intelligent here and determine that the restricted sensor is indeed active within the cluster.
Having to manually curate a separate ZIMonSensors.cfg because of this very inconvenient and error-prone. Any changes done via mmperfmon config update then have to be (manually) transferred to the exporter's separate config file to keep it uptodate.