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

Configurable metrics endpoint for prometheus output #3245

Merged
merged 1 commit into from
Sep 19, 2017
Merged

Configurable metrics endpoint for prometheus output #3245

merged 1 commit into from
Sep 19, 2017

Conversation

pcabido
Copy link
Contributor

@pcabido pcabido commented Sep 18, 2017

Make the metrics path configurable but /metrics by default. Using a non
default value can be useful when used in k8s pods with multiple containers
that have non standard prometheus metric paths.
Some apps already use /metrics for something else.

Required for all PRs:

  • [*] Signed CLA.
  • [*] Associated README.md updated.
  • [*] Has appropriate unit tests.

Make the metrics path configurable but /metrics by default. Using a non
default value can be useful when used in k8s pods with multiple containers
that have non standard prometheus metric paths.
Some apps already use /metrics for something else.
@danielnelson danielnelson added this to the 1.5.0 milestone Sep 18, 2017
@danielnelson
Copy link
Contributor

Code is good, I'm just curious about one thing: since the output is on its own port, why do you need the path to be different?

@pcabido
Copy link
Contributor Author

pcabido commented Sep 19, 2017

I need the path to be the same. The limitation I faced was that the main application we had running in some pods I was changing was exposing prometheus in a non standard path since /metrics was already being used for something else. This change allows consistency in such cases.

@danielnelson danielnelson merged commit decb09e into influxdata:master Sep 19, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants