Fedora Account System
Red Hat Associate
Red Hat Customer
Document URL: ============= Section Number and Name: Part V. Monitoring Chapter 10. Enabling Volume Metrics 10.1. Enabling Volume Metrics for File Storage and Block Storage. Describe the issue: =================== 10.1. Enabling Volume Metrics for File Storage and Block Storage needs update, the way Prometheus gets deployed and collects metrics has changed between OCP 3.10 and OCP 3.11. If you are using OCP 3.10, the doc details how to get all the information. If you are using OCP 3.11 it only collects a subset of metrics by default. we are not able to collect metrics. Suggestions for improvement: ============================ Steps to setup prometheus are no longer same in 3.10 and 3.11, this has to be updated accordingly. we need to have correct steps to configure prometheus to view volume and bricks metrics, with 3.11 its no longer possible.
Document URl: ============= https://access.redhat.com/documentation/en-us/openshift_container_platform/3.10/html-single/configuring_clusters/#openshift-prometheus
The problem with the suggested doc approach I see is that it creates an additional ServiceMonitor in the openshift-monitoring namespace. OpenShift docs explicitly state this as an unsupported operation (https://access.redhat.com/documentation/en-us/openshift_container_platform/3.11/html-single/configuring_clusters/#persistent-storage): Explicitly unsupported cases include: Creating additional ServiceMonitor objects in the openshift-monitoring namespace, thereby extending the targets the cluster monitoring Prometheus instance scrapes. This can cause collisions and load differences that cannot be accounted for, therefore the Prometheus setup can be unstable. We'd need a properly supported solution. How can we achieve this.
If there are any unique cases then the solution can be documented as a KCS article instead. In this case, I would request Vignesh to comment on creating an additional ServiceMonitor in the openshift-monitoring namespace, and if there are any better solutions.
*** Bug 1650499 has been marked as a duplicate of this bug. ***
*** Bug 1680108 has been marked as a duplicate of this bug. ***
Hello Patric, We discussed this during 3.11.2 time frame where we have tested the feature by enabling additional ServiceMonitor in the openshift-monitoring namespace and since ocp team does not support this we have not taken this request forward. Can you please let us know how do we proceed here ? Thanks kasturi
(In reply to RamaKasturi from comment #19) > Hello Patric, > > We discussed this during 3.11.2 time frame where we have tested the > feature by enabling additional ServiceMonitor in the openshift-monitoring > namespace and since ocp team does not support this we have not taken this > request forward. Can you please let us know how do we proceed here ? > > Thanks > kasturi OCP team agrees now to have an exception for OCS to add Service Monitors in the openshift-monitoring name space. So we're good to go ahead with this approach and document it.
*** Bug 1669486 has been marked as a duplicate of this bug. ***
Have updated the required content. Currently in peer review. Will update the doc link after final changes today. Sharing the Git link for reference: https://gitlab.cee.redhat.com/red-hat-gluster-storage-documentation/3.11_Red_Hat_Openshift_Container_Storage/merge_requests/246/diffs
Sharing the link for verification https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/3.11/html-single/Operations_guide/index?lb_target=preview#part-Monitoring Also sharing PDF incase the changes are not visible in the link.
Created attachment 1591935 [details] Operation guide Chapter 10. Enabling Volume Metrics in OpenShift 3.10 and 3.11
To check: 1. Open a new browser instance. 2. Go to access.redhat.com and log in 3. Copy the following URL into place: https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/3.11/html-single/operations_guide/index?lb_target=preview#part-Monitoring 4. Disable caching in your browser. Developer Tools > Network tab > Disable cache. (If you click on any links, check that "?lb_target=stage" still appears in the URL. If it doesn't, you're probably not seeing new content) Well, Kasturi I met up with Vignesh. Changes are not visible to Vignesh even though I am able to view it in the above link. Hence, pointing this out to Anjana S and tools team.
*** Bug 1644665 has been marked as a duplicate of this bug. ***