Bug 1741685

Summary: must-gather does not collect monitoring rules (PrometheusRule or ServiceMonitor) from openshift-* namespaces
Product: OpenShift Container Platform Reporter: Eric Rich <erich>
Component: MonitoringAssignee: Pawel Krupa <pkrupa>
Status: CLOSED ERRATA QA Contact: Junqi Zhao <juzhao>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.1.zCC: alegrand, anpicker, aos-bugs, erooth, jokerman, juzhao, mfojtik, mloibl, pkrupa, rvanderp, surbania
Target Milestone: ---   
Target Release: 4.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-01-23 11:05:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
servicemonitors/prometheusrules/alertmanagers/prometheuses info are collected by must-gather none

Description Eric Rich 2019-08-15 19:57:48 UTC 
Description of problem:

We don't seem to define the properly related resources within our operators for PrometheusRule or ServiceMonitor types. 

We should probably be gathering the following ServiceMonitor items: 

> NAMESPACE                                               NAME                  
> openshift-apiserver-operator                            openshift-apiserver-operator                           
> openshift-authentication-operator                       authentication-operator                                
> openshift-authentication                                oauth-openshift                                        
> openshift-controller-manager-operator                   openshift-controller-manager-operator                  
> openshift-controller-manager                            openshift-controller-manager                           
> openshift-dns                                           dns-default                                            
> openshift-image-registry                                image-registry                                         
> openshift-ingress                                       router-default                                         
> openshift-kube-apiserver-operator                       kube-apiserver-operator                                
> openshift-kube-apiserver                                monitor                                                
> openshift-kube-controller-manager-operator              kube-controller-manager-operator                       
> openshift-kube-controller-manager                       monitor                                                
> openshift-kube-scheduler-operator                       kube-scheduler-operator                                
> openshift-kube-scheduler                                monitor                                                
> openshift-monitoring                                    alertmanager                                           
> openshift-monitoring                                    cluster-monitoring-operator                            
> openshift-monitoring                                    cluster-version-operator                               
> openshift-monitoring                                    etcd                                                   
> openshift-monitoring                                    grafana                                                
> openshift-monitoring                                    kube-apiserver                                         
> openshift-monitoring                                    kube-controller-manager                                
> openshift-monitoring                                    kube-scheduler                                         
> openshift-monitoring                                    kube-state-metrics                                     
> openshift-monitoring                                    kubelet                                                
> openshift-monitoring                                    node-exporter                                          
> openshift-monitoring                                    openshift-apiserver                                    
> openshift-monitoring                                    prometheus                                             
> openshift-monitoring                                    prometheus-operator                                    
> openshift-monitoring                                    telemeter-client                                       
> openshift-operator-lifecycle-manager                    catalog-operator                                       
> openshift-operator-lifecycle-manager                    olm-operator                                           
> openshift-sdn                                           monitor-sdn                                            
> openshift-service-catalog-apiserver-operator            openshift-service-catalog-apiserver-operator           
> openshift-service-catalog-controller-manager-operator   openshift-service-catalog-controller-manager-operator  

We should probably be gathering the following PrometheusRule items: 

> NAMESPACE              NAME                  
> openshift-monitoring   prometheus-k8s-rules  


Version-Release number of selected component (if applicable): 4.1.11
Comment 2 Maciej Szulik 2019-08-16 15:05:18 UTC 
Sending it to monitoring team, since they own the code responsible for filling in the related objects.
Comment 10 Junqi Zhao 2019-11-29 06:37:45 UTC 
Created attachment 1640583 [details]
servicemonitors/prometheusrules/alertmanagers/prometheuses info are collected by must-gather
Comment 12 errata-xmlrpc 2020-01-23 11:05:05 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0062