-
Notifications
You must be signed in to change notification settings - Fork 858
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
Publish metrics to Prometheus and Grafana #256
Comments
|
These could be high-level considerations:
This is just an initial proposal. @JimBugwadia @shivdudhani Please add to the list if you have valuable cases. |
|
hi, i would suggest to support ServiceMonitor / PodMonitor of the prometheus operator. |
|
@realshuting , I don't think, as a part of this issue, we'd have to programme anything for grafana per se. Then, while using grafana, we just have to make it use the prometheus datasource which would be storing kyverno's metrics (exported in the first place by the custom exporter) Please correct me if I am wrong :) |
|
I think this task will also include thanos to make metrics globally available at a central place to present on Grafana. |
|
We should think about the use cases for different metric sets. I see at least 2 user stories:
There are likely others... Based on these concerns / use cases we can determine the appropriate metrics and dashboards / reports. |
|
See: https://github.com/fjogeleit/policy-reporter - this may help address some of the use cases mentioned. |
|
It would be good to have these metrics https://kubernetes.slack.com/archives/CLGR9BJU9/p1614050069016200?thread_ts=1614025217.009600&cid=CLGR9BJU9 to help tune the memory usage. |
|
@realshuting I guess we can close this one as well now |
|
Closed via #1877. |
Currently policy metrics are shown in the status. It would be good to expose a
/metricsendpoint that can be used by Prometheus to collect and aggregate metrics. A Grafana dashboard can then be used to display policy execution state and trends.The text was updated successfully, but these errors were encountered: