Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

jsonnet/node-exporter: adjust to node-exporter v1.2.0 arg name change #1407

Conversation

jan--f
Copy link
Contributor

@jan--f jan--f commented Sep 29, 2021

In version node-exporter v1.2.0
two argument name changes were introduced. While the old names still
work (with a deprecation warning), lets use the new names.

Signed-off-by: Jan Fajerski [email protected]

Description

Use --collector.filesystem.mount-points-exclude instead of deprecated --collector.filesystem.ignored-mount-points argument for node-exporter.

Type of change

  • CHANGE (fix or feature that would cause existing functionality to not work as expected)
  • FEATURE (non-breaking change which adds functionality)
  • BUGFIX (non-breaking change which fixes an issue)
  • ENHANCEMENT (non-breaking change which improves existing functionality)
  • NONE (if none of the other choices apply. Example, tooling, build system, CI, docs, etc.)

Changelog entry

- Use `--collector.filesystem.mount-points-exclude` instead of deprecated `--collector.filesystem.ignored-mount-points` argument for `node-exporter`.

In version [node-exporter v1.2.0](https://github.com/prometheus/node_exporter/releases/tag/v1.2.0)
two argument name changes were introduced. While the old names still
work (with a deprecation warning), lets use the new names.

Signed-off-by: Jan Fajerski <[email protected]>
Copy link
Contributor

@dgrisonnet dgrisonnet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks @jan--f.

@dgrisonnet
Copy link
Contributor

Now that we moved to automated component version update, I guess have been less careful about the changes introduced by each version so it would be great if we could attach the changelogs of the new versions to the PR that does the update. It would be easier to review the changes and prevent this kind of issue from occurring again in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants