-
Notifications
You must be signed in to change notification settings - Fork 344
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
Expose metrics to Prometheus #82
Comments
@astefanutti do you want to help ? |
@lburgazzoli for sure. I need to get into the codeline. If you have some direction or guidelines already, I'd be happy to follow your lead! |
I think you can try following the readme and the docs so we can also see what's missing there, then if you need help ping us on gitter |
I think it would be to leverage traits to configure Prometheus/Jolokia |
Agreed. That's what I had in mind a priori. |
The Prometheus trait has been created and should be available in next release (a priori 0.3.0). |
Fix rhi version to 2022.Q1 (metering label)
A common set of Camel-K related metrics could be exposed to Prometheus for monitoring purpose.
Besides, It would be cool if it'd be possible to define some custom Prometheus metrics, directly in the custom resource.
Problably the JMX Prometheus Java agent would have to be enabled (configurably) and fragments would look like:
The text was updated successfully, but these errors were encountered: