https://docs.google.com/document/d/16PEJy293Hqm7MiconeuDwX2IeQV7RSAFz7NysHZnmbo/edit?pli=1# Googel doc with QE feedback

http://jenkinscat.gsslab.pnq.redhat.com:8080/view/Devtools/job/doc-CodeReady-Workspaces_Admin-Guide/lastSuccessfulBuild/artifact/index.html#tracing-codeready-workspaces Section in downstream documentation

Read description of comment for "Tracing CRW"

Add additional installation/configuration steps for Jagger.

This needs to go into upstream first.
--------------------------------------------------------------

Comments:
"Mmusiien - 4.3. Enabling CodeReady Workspaces metrics collections
1) Prerequisites describes only the possibility to install directly from the official page of Jaegger, but we actually have more possible options how to do it:

a) - we can deploy Jugger form the CHE project for instance:

oc new-app -f ${CHE_LOCAL_GIT_REPO}/deploy/openshift/templates/jaeger-all-in-one-template.yml

b) we can deploy Jugger with OperatorHub on Openshift 4.1, 4.2 versions

2 . In procedure section
"Enable the following environment variables for CodeReady Workspaces deployment:"

This look like it will work if it is deployed without operator. Otherwise the Workspaces deployment will be restored to previous state. In this case we should add the variables into СheCluster section."