Skip to content

[BUG] No Custom Paths for EDAC scraping #3633

@andysharma24

Description

@andysharma24

I noticed that the edac scraping in node-exporter is hard coded to a path.

var (
	edacMemControllerRE = regexp.MustCompile(`.*devices/system/edac/mc/mc([0-9]*)`)
	edacMemCsrowRE      = regexp.MustCompile(`.*devices/system/edac/mc/mc[0-9]*/csrow([0-9]*)`)
)

from this file. I believe this is a bug/oversight as we can set the actual sysfs with args, but not the path that the edac is scraped from.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions