Flag '--web.disable-exporter-metrics' is not disabling 'promhttp_metric_handler_errors_total' metric

[mstoetzer]

node_exporter version:

node_exporter, version 1.3.0 (branch: HEAD, revision: c65f870ef90a4088210af0319498b832360c3366)
  build user:       root@4801f8f250a6
  build date:       20211118-16:34:14
  go version:       go1.17.3
  platform:         linux/amd64

node_exporter command line flags

[Unit]
Description=Node Exporter
After=network.target

[Service]
User=node_exporter
Group=node_exporter
ExecStart=/usr/local/bin/node_exporter \
  --collector.processes \
  --collector.textfile.directory="/var/lib/node_exporter/textfile_collector" \
  --web.disable-exporter-metrics \
  --web.listen-address="0.0.0.0:9100"

[Install]
WantedBy=multi-user.target

Are you running node_exporter in Docker?

Nope.

What did you do that produced an error?

Added the commandline flag '--web.disable-exporter-metrics', that disables promhttp_, process_, go_ metrics.

What did you expect to see?

The following metric should not be printed:

# HELP promhttp_metric_handler_errors_total Total number of internal errors encountered by the promhttp metric handler.
# TYPE promhttp_metric_handler_errors_total counter
promhttp_metric_handler_errors_total{cause="encoding"} 0
promhttp_metric_handler_errors_total{cause="gathering"} 0

[Aeres-u99]

Having similar issue on this one:

Command:

vagrant@debian-10  ~  ./node_exporter --collector.disable-defaults --web.disable-exporter-metrics --collector.textfile --collector.textfile.directory="./collection"
ts=2022-10-13T06:10:44.626Z caller=node_exporter.go:182 level=info msg="Starting node_exporter" version="(version=1.4.0, branch=HEAD, revision=7da1321761b3b8dfc9e496e1a60e6a476fec6018)"
ts=2022-10-13T06:10:44.626Z caller=node_exporter.go:183 level=info msg="Build context" build_context="(go=go1.19.1, user=root@83d90983e89c, date=20220926-12:32:56)"
ts=2022-10-13T06:10:44.626Z caller=node_exporter.go:108 level=info msg="Enabled collectors"
ts=2022-10-13T06:10:44.626Z caller=node_exporter.go:115 level=info collector=textfile
ts=2022-10-13T06:10:44.626Z caller=node_exporter.go:199 level=info msg="Listening on" address=:9100
ts=2022-10-13T06:10:44.626Z caller=tls_config.go:195 level=info msg="TLS is disabled." http2=false

Output:

curl -s http://192.168.0.101:9100/metrics | grep -v '^#'
myscript_duration_seconds 10
myscript_last_run_seconds 1.665640908e+09
node_exporter_build_info{branch="HEAD",goversion="go1.19.1",revision="7da1321761b3b8dfc9e496e1a60e6a476fec6018",version="1.4.0"} 1
node_scrape_collector_duration_seconds{collector="textfile"} 0.000126785
node_scrape_collector_success{collector="textfile"} 1
node_textfile_mtime_seconds{file="collection/myscript.prom"} 1.665640908e+09
node_textfile_scrape_error 0
promhttp_metric_handler_errors_total{cause="encoding"} 0
promhttp_metric_handler_errors_total{cause="gathering"} 0

Version:

./node_exporter --version
node_exporter, version 1.4.0 (branch: HEAD, revision: 7da1321761b3b8dfc9e496e1a60e6a476fec6018)
  build user:       root@83d90983e89c
  build date:       20220926-12:32:56
  go version:       go1.19.1
  platform:         linux/amd64

EDIT: Added version details

[fede843]

I can see that metric still not honoring the command flag;

docker exec node-exporter node_exporter --version
node_exporter, version 1.6.1 (branch: HEAD, revision: 4a1b77600c1873a8233f3ffb55afcedbb63b8d84)
  build user:       root@586879db11e5
  build date:       20230717-12:10:52
  go version:       go1.20.6
  platform:         linux/amd64
  tags:             netgo osusergo static_build

...
# TYPE node_vmstat_pswpin untyped
node_vmstat_pswpin 1.2156561e+07
# HELP node_vmstat_pswpout /proc/vmstat information field pswpout.
# TYPE node_vmstat_pswpout untyped
node_vmstat_pswpout 3.854824e+07
# HELP promhttp_metric_handler_errors_total Total number of internal errors encountered by the promhttp metric handler.
# TYPE promhttp_metric_handler_errors_total counter
promhttp_metric_handler_errors_total{cause="encoding"} 0
promhttp_metric_handler_errors_total{cause="gathering"} 0

The rest node related is gone, as expected, but this one still there.