On Mon, 02 Feb 2026 18:42:47 +0000 [email protected] wrote:
> after taking another pass at this issue, somebody pointed out that the Debian patches are indeed responsible for this behaviour: https://salsa.debian.org/go-team/packages/prometheus-node-exporter/-/blob/debian/sid/debian/patches/0001-Debian-defaults.patch?ref_type=heads
>> These changes were migrated as part of report #908811. Now I wonder, are these overridden defaults still necessary today? The information scraped by this service should be cached by the kernel anyway, so waking up disks should not be the issue (anymore)?
Looping in Tina, since she was the author of that patch.I guess the reason for excluding /media is that it typically has removable media dynamically mounted there, and usually you don't want such things to pollute your metrics. Using /mnt for permanently mounted filesystems is also a bit of an antipattern these days. At least in my experience, I would only ever mount something under /mnt temporarily, typically when trying to rescue a system or perform some data recovery (i.e. attaching a backup volume).
Of course, in the rare case that somebody is using /mnt for "production" filesystems, it is fairly trivial to override the default excluded mountpoints via command line args in /etc/default/prometheus-node-exporter.
I am undecided whether it was wise to move them to a source code patch, rather than ship them as a default option in ARGS.
OpenPGP_signature.asc
Description: OpenPGP digital signature
