Uploaded image for project: 'OpenShift Service Mesh'
  1. OpenShift Service Mesh
  2. OSSM-2442

No way to configure custom metrics in telemetry v2

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Normal Normal
    • None
    • OSSM 2.1.0
    • Maistra, Sail Operator
    • False
    • False

      Users that have custom metrics in 2.0 or 1.1 cannot achieve the same result in 2.1 because there's no mixer anymore and we don't support a way to edit the EnvoyFilter. It's a regression.

      Upstream documentation instructs users to edit the Istio Operator Custom Resource.

      We could do the same with our SMCP. Charts are already prepared. We just need to expose .values.telemetry.v2.prometheus.configOverride in SMCP, under .spec.telemetry.

            [OSSM-2442] No way to configure custom metrics in telemetry v2

            Rob Cernich added a comment - - edited

            As a temporary workaround in 2.1.0, users could use the technologyPreview field in SMCP:

            spec: 
              techPreview: 
                telemetry: 
                  v2:
                    prometheus: 
                      configOverride: 
                        inboundSidecar: <inbound-sidecar-metric-json-config>
                        outboundSidecar: <outbound-sidecar-metric-json-config>
                        gateway: <gateway-metric-json-config>

             

            Rob Cernich added a comment - - edited As a temporary workaround in 2.1.0, users could use the technologyPreview field in SMCP: spec: techPreview: telemetry: v 2 : prometheus: configOverride: inboundSidecar: <inbound-sidecar-metric-json-config> outboundSidecar: <outbound-sidecar-metric-json-config> gateway: <gateway-metric-json-config>  

            cc jlongmui@redhat.com

            I wouldn't consider this a blocker for 2.1.  If necessary, the spec.techPreview field could be used in the short term as a workaround.

            Rob Cernich added a comment - cc jlongmui@redhat.com I wouldn't consider this a blocker for 2.1.  If necessary, the spec.techPreview field could be used in the short term as a workaround.

              Unassigned Unassigned
              jsantana@redhat.com Jonh Wendell
              Votes:
              7 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: