jianrongzhang89 commented on code in PR #540:
URL: 
https://github.com/apache/incubator-kie-kogito-serverless-operator/pull/540#discussion_r1804991007


##########
internal/controller/profiles/common/object_creators.go:
##########
@@ -439,10 +443,37 @@ func UserPropsConfigMapCreator(workflow 
*operatorapi.SonataFlow) (client.Object,
 
 // ManagedPropsConfigMapCreator creates an empty ConfigMap to hold the 
external application properties
 func ManagedPropsConfigMapCreator(workflow *operatorapi.SonataFlow, platform 
*operatorapi.SonataFlowPlatform) (client.Object, error) {
-
        props, err := properties.ApplicationManagedProperties(workflow, 
platform)
        if err != nil {
                return nil, err
        }
        return workflowproj.CreateNewManagedPropsConfigMap(workflow, props), nil
 }
+
+// ServiceMonitorCreator is an ObjectsCreator for Service Monitor for the 
workflow service.
+func ServiceMonitorCreator(workflow *operatorapi.SonataFlow) (client.Object, 
error) {
+       lbl := workflowproj.GetMergedLabels(workflow)
+       spec := &prometheus.ServiceMonitorSpec{
+               Selector: metav1.LabelSelector{
+                       MatchLabels: map[string]string{

Review Comment:
   @wmedvede The selector defined in the servicemonitor's spec is used for 
Prometheus to identify the k8s services that it uses to scrape the metrics, and 
hence I'd like to keep the selector with the minimal set of the labels, and 
adding the remaining labels as part of the selector might have some performance 
impact on the Prometheus scraping process. My preference is to keep it as it 
is. What do you think?



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to