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
[feature/monitoring] Implement /metrics for the operator. #4
Conversation
…k-operator into feature/monitoring
…k-operator into feature/monitoring
… into feature/monitoring
… into feature/monitoring
… into feature/monitoring
42e622d
to
d7f9d91
Compare
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.
Great work overall!
Most of the issues are cosmetic changes.
I did not list some issues found with linter, as those can be always checked by running the scan.
Other things that should be fixed would be to add proper error wrapping (not sure if I found all the places where that should be done), add comments to the exported structs/functions etc. and remove redundant code that is commented out.
Co-authored-by: p-strusiewiczsurmacki-mobica <137421299+p-strusiewiczsurmacki-mobica@users.noreply.github.com>
… into feature/monitoring
Co-authored-by: p-strusiewiczsurmacki-mobica <137421299+p-strusiewiczsurmacki-mobica@users.noreply.github.com>
Co-authored-by: p-strusiewiczsurmacki-mobica <137421299+p-strusiewiczsurmacki-mobica@users.noreply.github.com>
The only thing which currently does not work is the end2end route export stuff in the lab which is provided with this Pull Request. For that I would need @chdxD1 to check and fix. But this could also be done later. |
Co-authored-by: Kai <kai@naschinski.de>
Co-authored-by: Kai <kai@naschinski.de>
Co-authored-by: Kai <kai@naschinski.de>
Some information on exported metrics and how they are exported.
metrics.txt