Allow Prometheus exporter to be used without HTTP server #551
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CallumTodd7
requested review from
nachoBonafonte,
bryce-b and
vvydier
as code owners
The committers listed above are authorized under a signed CLA. |
nachoBonafonte
approved these changes
Jun 30, 2024
vvydier
approved these changes
Jul 1, 2024
|
LGTM, thanks for your contribution. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently the only way to use the Prometheus exporter is via
PrometheusExporterHttpServer.PrometheusExporterHttpServercallsPrometheusExporterExtensions.writeMetricsCollectionto do the heavy lifting of building the response payload string. Allowing library users access to this function would allow for different/existing HTTP server frameworks to be used.