Description of problem: The Jaeger Operator is installed as a prerequisite of Red Hat Service Mesh for OpenShift, and as such, we don’t have a clear view on how Jaeger is being used, and as such, how much value we are bringing to the product. Given that we might not have the appropriate data in place, we need to better instrument the Jaeger Operator to provide information such as: How many Jaeger instances (CRs) are managed per operator Which strategies are being used (all in one, production, streaming) Which agent modes are being used (daemonset, sidecar) Which storages are being used (ES is the only supported one, but are people actually using others?) Version-Release number of selected component (if applicable):4.9 How reproducible: N/A Steps to Reproduce: N/A Actual results: N/A Expected results: N/A Additional info: N/A
The jaeger metrics are in the rhobs configuration now [1]. Ruben, can you move it back to MODIFIED and assign this bugzilla to the Jaeger QE as asked in comment 2? [1] https://github.com/rhobs/configuration/blob/38b14d595c15e13d358b4256f919150a9d0edb33/configuration/telemeter/metrics.json#L59-L61
Changing to 4.9.0 since though the change wasn't verified in time, the code already merged before 4.9 GA (https://github.com/openshift/cluster-monitoring-operator/blob/release-4.9/manifests/0000_50_cluster-monitoring-operator_04-config.yaml#L564-L578).
set to VERIFIED based on comment 2 and comment 8, and we can find the jaeger metrics in comment 2 from telemeter server now
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 (OpenShift Container Platform 4.9.10 bug fix update), 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-2021:4889