Currently, the official doc as well as the upstream  doc, assumes the existence of a dedicated instance of the Prometheus service for the 3scale service. 

Starting with Openshift 4.6, you can  define monitoring for user-defined projects

OCP 4.6: https://docs.openshift.com/container-platform/4.6/monitoring/enabling-monitoring-for-user-defined-projects.html

OCP 4.10 https://docs.openshift.com/container-platform/4.10/monitoring/enabling-monitoring-for-user-defined-projects.html

The Thanos Querier should enable 3scale dashboards and 3scale Prometheus Rules (alerts) work out of the box when involved metrics are composed of a) 3scale custom metrics and b) platform metrics (like CPU, mem usage, ...)

The job would be exploring the feasibility of leveraging the platform's default prometheus instance to monitor 3scale. Specifically, ensure that:

• 3scale custom metrics are being scrapped
• 3scale Dashboards have metrics
• 3scale Prometheus rules are fired when thresholds are exceeded.

If platform user workload monitoring can be leveraged, update upstream doc accordingly and doc team should also change official doc. The alerts should be now managed by the platforms default alert manager. That also should be updated in the doc

Check out if any change should be done in 3scale dashboards and Prometheus Rules regarding the new data source (the Thanos querier)

Related links:

• How to configure OpenShift Monitoring/Grafana to monitor 3scale
  • https://access.redhat.com/articles/6588231
• Prometheus integration for OpenShift 4.6

• • https://issues.redhat.com/browse/THREESCALE-7087
• Monitoring without the need of grafana operator

• • https://issues.redhat.com/browse/THREESCALE-7101
•