-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Serve metrics from the local registry in the diagnostic service #51031
Serve metrics from the local registry in the diagnostic service #51031
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any chance we could catch this through testing?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 for adding some test for either the handler or the combined gatherer - or maybe even actually hitting /metrics
on a running Teleport?
Done in 66970e8
Yup, that's what the metrics service test was doing, I mostly copied it and made it query the diagnostic service instead. The code is a bit duplicated but I don't think the deduplicating this test code is worth the time and complexity. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, Hugo.
* Use local metrics registry in the diagnostic service * Test metrics are served by the diag service
* Use local metrics registry in the diagnostic service * Test metrics are served by the diag service
* Use local metrics registry in the diagnostic service * Test metrics are served by the diag service
* Use local metrics registry in the diagnostic service * Test metrics are served by the diag service
* Use local metrics registry in the diagnostic service * Test metrics are served by the diag service
In #50913 I added a local registry and assumed the metrics service was serving the metrics. It appears this is handled by default by the diagnostics service. The metrics service is undocumented (in the config reference) and disabled by default.
This PR: