Lustre2 plugin proc/sys path names changed

[omgold]

Relevant telegraf.conf

[[inputs.lustre2]]
 ## An array of /proc globs to search for Lustre stats
  ## If not specified, the default will work on Lustre 2.12.x
  ##
  # mgs_procfiles = [
  #   "/sys/fs/lustre/mgs/*/eviction_count",
  # ]
  # ost_procfiles = [
  #   "/proc/fs/lustre/obdfilter/*/stats",
  #   "/proc/fs/lustre/osd-ldiskfs/*/stats",
  #   "/proc/fs/lustre/obdfilter/*/job_stats",
  #   "/proc/fs/lustre/obdfilter/*/exports/*/stats",
  #   "/proc/fs/lustre/osd-ldiskfs/*/brw_stats",
  #   "/proc/fs/lustre/osd-zfs/*/brw_stats",
  #   "/sys/fs/lustre/odbfilter/*/eviction_count",
  # ]
  # mds_procfiles = [
  #   "/proc/fs/lustre/mdt/*/md_stats",
  #   "/proc/fs/lustre/mdt/*/job_stats",
  #   "/proc/fs/lustre/mdt/*/exports/*/stats",
  #   "/proc/fs/lustre/osd-ldiskfs/*/brw_stats",
  #   "/proc/fs/lustre/osd-zfs/*/brw_stats",
  #   "/sys/fs/lustre/mdt/*/eviction_count",
  # ]

Logs from Telegraf

Nothing interesting here, because missing files get ignored

System info

Telegraf 1.39.3, Rocky 9.8, Lustre 2.17.0

Docker

Lustre changed the paths for the ost_procfiles and mdt_procfiles (again), so the defaults of the plugin don't work anymore.

Changes as of Lustre (2.17.0):

/proc/fs/lustre/mdt/*/exports/*/stats -> /sys/kernel/debug/lustre/mdt/*/exports/*/stats
/proc/fs/lustre/obdfilter/*/exports/*/stats -> /sys/kernel/debug/lustre/obdfilter/*/exports
/proc/fs/lustre/obdfilter/*/stats -> /sys/kernel/debug/lustre/osd-zfs/*/stats
/proc/fs/lustre/osd-ldiskfs/*/brw_stats -> /sys/kernel/debug/lustre/osd-ldiskfs/*/brw_stats
/proc/fs/lustre/osd-ldiskfs/*/stats -> /sys/kernel/debug/lustre/osd-ldiskfs/*/stats
/proc/fs/lustre/osd-zfs/*/brw_stats -> /sys/kernel/debug/lustre/osd-zfs/*/brw_stats

Steps to reproduce

1. Run the lustre2 plugin with default settings

Expected behavior

All metrics mentioned in the plugin documentation are collected.

Actual behavior

The metrics from the renamed files are missing.

Additional info

No response

[srebhan]

@omgold why don't you use the settings to correct the paths? Currently there is no "auto-detection" of the version nor of the paths. If we had testcases, that is a snapshot of the relevant files and directory structure, we might be able to work on this...