log.level setting is debug and --log.level flag is ignored

[Kay]

The blackbox_exporter from the ubuntu jammy repository always logs with level 'debug' and ignores the flag to change the logging level.

# lsb_release -rd
Description: Ubuntu 22.04 LTS
Release: 22.04

# apt-cache policy prometheus-blackbox-exporter
prometheus-blackbox-exporter:
  Installed: 0.19.0-1
  Candidate: 0.19.0-1
  Version table:
 *** 0.19.0-1 500
        500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
        100 /var/lib/dpkg/status

Expected behavior:

Starting the exporter via

# /usr/bin/prometheus-blackbox-exporter --web.listen-address=":9116" --log.level=error --config.file /etc/prometheus/blackbox.yml

and connecting interacting with it, e.g.

# curl -s 'localhost:9116/probe?module=tcp_connect&target=8.8.8.8:53'

Should only give output of level 'error' (nothing for me in this case). The original exporter

# wget 'https://github.com/prometheus/blackbox_exporter/releases/download/v0.19.0/blackbox_exporter-0.19.0.linux-amd64.tar.gz'

shows this behavior.

What happens instead:

Output of all levels, including 'debug' is returned on startup and when the exporter is queried

# ts=2022-07-22T21:32:36.105Z caller=main.go:224 level=info msg="Starting blackbox_exporter" version="(version=0.19.0, branch=debian/sid, revision=0.19.0-1)"
# ...
# ts=2022-07-22T21:32:36.107Z caller=main.go:259 level=debug routePrefix=/
# ...
# ts=2022-07-22T21:32:37.955Z caller=main.go:180 module=tcp_connect target=8.8.8.8:53 level=debug msg="Beginning probe" probe=tcp timeout_seconds=119.5

[James Dingwall (a-james-launchpad)]

See also: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010054

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[James Dingwall (a-james-launchpad)]

I'm getting a syslog of ~2GB / week due to all the messages being recorded since upgrading to jammy.

[Giuseppe Petralia (peppepetra)]

Hitting this on jammy version 0.19.0-1ubuntu0.2 too