Bug#1032329: prometheus-node-exporter: --collector.netdev.device-include cannot be used

[Daniel Swarbrick]

You can use --collector.netdev.device-include if you simply ensure that 
--collector.netdev.device-exclude is empty, e.g.:


prometheus-node-exporter --collector.netdev.device-exclude= 
--collector.netdev.device-include=eno1




OpenPGP_signature
Description: OpenPGP digital signature

Bug#1032329: prometheus-node-exporter: --collector.netdev.device-include cannot be used

[Christoph Anton Mitterer]

Package: prometheus-node-exporter
Version: 1.1.2+ds-2.1
Severity: important


Hey.

Since Debian seems to set a default falue to --collector.netdev.device-exlude,
--collector.netdev.device-include can never be used, as the two are mutually
exclusive and when setting the latter in /etc/default/prometheus-node-exporter
the service just fails with:
Mar 04 05:40:21 lcg-lrz-dcache0 prometheus-node-exporter[1048667]: panic: 
Couldn't create metrics handler: couldn't create collector: device-exclude & 
device-include are mutually exclusive

I guess the same is the case for other such mutually exclusive options
where you give a default.

Can this be fixed for bookwork, too?

Cheers,
Chris.