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

node_exporter.pp does not provide direct way to override the listening port #692

Open
lchopfpt opened this issue Aug 22, 2023 · 0 comments
Assignees

Comments

@lchopfpt
Copy link

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet: 6.26.1
  • Ruby:
  • Distribution:
  • Module version: 13.3.0

How to reproduce (e.g Puppet code you use)

Can't provide a negative. While there's the ability to change "scrape_port" which is used to provide an exported resource to prometheus server, that scrape_port value is not used elsewhere, so then node_exporter still listens on its default.

What are you seeing

No override of the listening port in a direct manner that will update both runtime setting of web.listen-address and scrape_port.
It can be provided as part of "extra_options" but then one must still also update scrape_port too.

What behaviour did you expect instead

To be able to set one value for port and have it reflect in the runtime of the service and its listening port as well as what is exported as a resource to prometheus server.

Output log

Any additional information you'd like to impart

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

No branches or pull requests

2 participants