Bug 1671843

Summary:	Add 3rd party servicemonitor to Prometheus in OCP 3.11
Product:	OpenShift Container Platform	Reporter:	Tony Garcia <antgarci>
Component:	RFE	Assignee:	Christian Heidenreich <cvogel>
Status:	CLOSED WONTFIX	QA Contact:	Xiaoli Tian <xtian>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.11.0	CC:	aos-bugs, jokerman, mmccomas
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-12 11:57:53 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:

Description Tony Garcia 2019-02-01 20:42:13 UTC

Description of problem:
Add 3rd party servicemonitor to Prometheus in OCP 3.11


Version-Release number of selected component (if applicable):
3.11

How reproducible:
3rd party servicemonitors have been added, but according to the 3.11 documentation, adding other service monitors is not supported.

"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."

https://docs.openshift.com/container-platform/3.11/install_config/prometheus_cluster_monitoring.html#supported-configuration


Additional info:
An RH consultant on-site was able to add a Prometheus to scrap Portworx by following the instructions in this link:
https://isolate.menlosecurity.com/https:/docs.portworx.com/portworx-install-with-kubernetes/operate-and-maintain-on-kubernetes/monitoring/monitoring-px-prometheusandgrafana.1/#install-the-service-monitor

The customer needs the ability to add this servicemonitor due to the size of the  OCP environment.

Comment 2 Christian Heidenreich 2019-02-05 09:01:48 UTC

In 3.11, the cluster-monitoring stack is not intended to be extended with new objects such as a ServiceMonitor. Therefore, this will unfortunately not happening in this version. OpenShift users have successfully been able to spin up their own Prometheus for additional monitoring requirements.

We are currently investigating mechanisms to give customers a more flexible approach to easily monitor additional services side by side with the cluster-related services. That will likely to be happen in 4.x though.

Comment 4 Kirsten Newcomer 2019-06-12 11:57:53 UTC

With the introduction of OpenShift 4, Red Hat has delivered or roadmapped a substantial number of features based on feedback by our customers.  Many of the enhancements encompass specific RFEs which have been requested, or deliver a comparable solution to a customer problem, rendering an RFE redundant.

This bz (RFE) has been identified as a feature request not yet planned or scheduled for an OpenShift release and is being closed. 

If this feature is still an active request that needs to be tracked, Red Hat Support can assist in filing a request in the new JIRA RFE system, as well as provide you with updates as the RFE progress within our planning processes. Please open a new support case: https://access.redhat.com/support/cases/#/case/new 

Opening a New Support Case: https://access.redhat.com/support/cases/#/case/new 

As the new Jira RFE system is not yet public, Red Hat Support can help answer your questions about your RFEs via the same support case system.