-
Epic
-
Resolution: Done
-
Major
-
None
-
Integration into OCP monitoring
-
To Do
-
25% To Do, 0% In Progress, 75% Done
Goal: Quay leverages the OCP built-in monitoring capabilities
Problem:
- as of today customers can't use the OpenShift monitoring capabilities for Quay if Quay runs on OCP or one of the Quay operators (CSO, integration operator) runs there
Why is this important:
- Extends the value of OpenShift using Quay
- Extends the value of Quay if used in conjunction with OpenShift
- avoids double-efforts of building our own monitoring solution
Dependencies (internal and external):
- OpenShift monitoring prerequisites
- Custom OpenShift monitoring dashboards
Acceptance Criteria
- Integration with OCP's built-in Prometheus and Grafana automatically
- Expose the metrics to OCP cluster monitoring
- Grafana dashboard with a 'lite' version of what AppSRE uses today for quay.io
- Able to use OCP's custom dashboard feature to create your own Quay dashboard
- Consider additional metrics (e.g. CSO vulns) that might make sense.
Open Questions:
- any Clair metrics that we could/should export to drive health analysis?
- blocks
-
PROJQUAY-288 OpenShift Console alerting triggered by various Quay events
- New
- incorporates
-
PROJQUAY-880 Monitoring and alerting based on metrics thresholds
- Closed