-
Bug
-
Resolution: Done
-
Major
-
DO328 - Early Access
-
None
-
ILT, ROLE, VT
-
en-US (English)
URL:
Reporter RHNID: rhn-gls-rtaniguchi
Section: - Lab: Observing an OpenShift Service Mesh
Language: en-US (English)
Workaround:
Description: This sentence does not make sense:
Although distributed tracing was enabled for services that you originally deployed, you will
clone the source code for the problematic microservice from GitHub and enable distributed
tracing as a part of this lab.
So according to this sentence, it says that distributed tracing is enabled on services I deployed.
But at the same time, this sentence says, that there is a problematic microservice that we need to enable tracing. Is this microservice a new one? or one of the existing ones running? Is the first sentence wrong?
In the following sentence, it requires some polishing:
Identify the microservice that is causing the slow response time in the Historical Data page.
From the traces and spans in the Jaeger console, you can identify the function name that is
causing the slowdown.
The microservice was identified before, when we clicked the Historical Data. What we need to identify is what method is causing the slowness.