Dear Maintainer,

   * What led up to the situation?

   Standard prometheus installation - server and clients Debian/trixie (Raspberry Pi OS/trixie)

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

   Search for the metrics for `node_filesystem_free_bytes` in the prometheus web interface

   * What was the outcome of this action?

   The node_filesystem_free_bytes metrics for Debian/Raspios clients do not appear in
   prometheus-db

   * What outcome did you expect instead?

   If I pass --no-collector.netstat as an argument (/etc/default/prometheus-node-exporter),
   the metrics for node_filesystem_free_bytes is recorded in the database, and can be
   queried.

   As a further point, this might indicate what the problem could be ??

   I’m using a script that, on a NAT router (OpenWRT), queries the prometheus-node-exporter
   clients via curl and then sends the data to a prometheus-push-gateway, again via curl.

   And there I get the following error message:

   # /etc/prometheus-openwrt_nat-scraper.sh

   pushed metrics are invalid or inconsistent with existing metrics: 30 error(s) occurred:
   * collected metric "node_netstat_TcpExt_SyncookiesSent" { label:{name:"instance"  value:"waals-pi5_prisma_pro_qms"}  label:{name:"job"  value:"waals_nat"}  untyped:{value:0}} is not a GAUGE
   * collected metric "node_netstat_Tcp_InErrs" { label:{name:"instance"  value:"waals-pi5_prisma_pro_qms"}  label:{name:"job"  value:"waals_nat"}  untyped:{value:0}} is not a GAUGE

   [cut cut]

   curl: (18) transfer closed with outstanding read data remaining

   Maybe this is also the problem with the default setup !?