Merge pull request #40980 from JStickler/OSSMDOC-456A

OSSMDOC-456: Distributed tracing rebranding work in OSSM docs.

Author: JStickler

_attributes/distr-tracing-document-attributes.adoc

@@ -12,6 +12,8 @@
 :product-dedicated: Red Hat OpenShift Dedicated
 :console-redhat-com: Red Hat OpenShift Cluster Manager
 
+:ProductName: Red Hat OpenShift Service Mesh
+
 :DTProductName: Red Hat OpenShift distributed tracing
 :DTShortName: distributed tracing
 :DTProductVersion: 2.1

distr_tracing/distr_tracing_install/distr-tracing-deploying-jaeger.adoc

@@ -58,6 +58,11 @@ include::modules/distr-tracing-deploy-production-es.adoc[leveloffset=+1]
 
 include::modules/distr-tracing-deploy-streaming.adoc[leveloffset=+1]
 
+[id="validating-your-jaeger-deployment"]
+== Validating your deployment
+
+include::modules/distr-tracing-accessing-jaeger-console.adoc[leveloffset=+1]
+
 [id="customizing-your-deployment"]
 == Customizing your deployment
 

distr_tracing/distr_tracing_install/distr-tracing-deploying-otel.adoc

@@ -11,3 +11,8 @@ The {OTELName} Operator uses a custom resource definition (CRD) file that define
 // The following include statements pull in the module files that comprise the assembly.
 
 include::modules/distr-tracing-config-otel-collector.adoc[leveloffset=+1]
+
+[id="validating-your-otel-deployment"]
+== Validating your deployment
+
+include::modules/distr-tracing-accessing-jaeger-console.adoc[leveloffset=+1]

modules/distr-tracing-accessing-jaeger-console.adoc

@@ -0,0 +1,60 @@
+////
+Module included in the following assemblies:
+
+////
+
+[id="distr-tracing-accessing-jaeger-console_{context}"]
+= Accessing the Jaeger console
+
+To access the Jaeger console you must have either {ProductName} or {DTProductName} installed, and {JaegerName} installed, configured, and deployed.
+
+The installation process creates a route to access the Jaeger console.
+
+If you know the URL for the Jaeger console, you can access it directly.  If you do not know the URL, use the following directions.
+
+.Procedure from OpenShift console
+. Log in to the {product-title} web console as a user with cluster-admin rights. If you use {product-dedicated}, you must have an account with the `dedicated-admin` role.
+
+. Navigate to *Networking* -> *Routes*.
+
+. On the *Routes* page, select the control plane project, for example `tracing-system`, from the *Namespace* menu.
++
+The *Location* column displays the linked address for each route.
++
+. If necessary, use the filter to find the `jaeger` route.  Click the route *Location* to launch the console.
+
+. Click *Log In With OpenShift*.
+
+////
+.Procedure from Kiali console
+
+. Launch the Kiali console.
+
+. Click *Distributed Tracing* in the left navigation pane.
+
+. Click *Log In With OpenShift*.
+////
+
+.Procedure from the CLI
+
+. Log in to the {product-title} CLI as a user with the `cluster-admin` role. If you use Red Hat OpenShift Dedicated, you must have an account with the `dedicated-admin` role.
++
+[source,terminal]
+----
+$ oc login https://<HOSTNAME>:6443
+----
++
+. To query for details of the route using the command line, enter the following command. In this example, `tracing-system` is the control plane namespace.
++
+[source,terminal]
+----
+$ export JAEGER_URL=$(oc get route -n tracing-system jaeger -o jsonpath='{.spec.host}')
+----
++
+. Launch a browser and navigate to ``\https://<JAEGER_URL>``, where `<JAEGER_URL>` is the route that you discovered in the previous step.
+
+. Log in using the same user name and password that you use to access the {Product-title} console.
+
+. If you have added services to the service mesh and have generated traces, you can use the filters and *Find Traces* button to search your trace data.
++
+If you are validating the console installation, there is no trace data to display.

modules/distr-tracing-config-ingester.adoc

@@ -42,7 +42,7 @@ The deadlock interval is disabled by default (set to `0`), to avoid terminating
 |options:
   log-level:
 |Logging level for the Ingester.
-|Possible values: `trace`, `debug`, `info`, `warning`, `error`, `fatal`, `panic`.
+|Possible values: `debug`, `info`, `warn`, `error`, `fatal`, `dpanic`, `panic`.
 |===
 
 .Streaming Collector and Ingester example

modules/distr-tracing-config-jaeger-collector.adoc

@@ -62,5 +62,5 @@ The Collectors are stateless and thus many instances of Jaeger Collector can be
 |options:
   log-level:
 |Logging level for the Collector.
-|Possible values: `debug`, `info`, `warning`, `error`, `fatal`, `panic`.
+|Possible values: `debug`, `info`, `warn`, `error`, `fatal`, `panic`.
 |===

modules/distr-tracing-config-query.adoc

@@ -39,14 +39,14 @@ Query is a service that retrieves traces from storage and hosts the user interfa
 |options:
   log-level:
 |Logging level for Query.
-|Possible values: `debug`, `info`, `warning`, `error`, `fatal`, `panic`.
+|Possible values: `debug`, `info`, `warn`, `error`, `fatal`, `panic`.
 |
 
 |options:
   query:
     base-path:
 |The base path for all jaeger-query HTTP routes can be set to a non-root value, for example, `/jaeger` would cause all UI URLs to start with `/jaeger`. This can be useful when running jaeger-query behind a reverse proxy.
-|/{path}
+|/<path>
 |
 |===
 

modules/jaeger-architecture.adoc

@@ -6,9 +6,9 @@ This CONCEPT module included in the following assemblies:
 ////
 
 [id="jaeger-architecture_{context}"]
-= Jaeger architecture
+= Distributed tracing architecture
 
-Jaeger is made up of several components that work together to collect, store, and display tracing data.
+The {JaegerShortName} is based on the open source link:https://www.jaegertracing.io/[Jaeger project]. The {JaegerShortName} is made up of several components that work together to collect, store, and display tracing data.
 
 * *Jaeger Client* (Tracer, Reporter, instrumented application, client libraries)- Jaeger clients are language specific implementations of the OpenTracing API. They can be used to instrument applications for distributed tracing either manually or with a variety of existing open source frameworks, such as Camel (Fuse), Spring Boot (RHOAR), MicroProfile (RHOAR/Thorntail), Wildfly (EAP), and many more, that are already integrated with OpenTracing.
 

modules/jaeger-config-collector.adoc

@@ -62,5 +62,5 @@ The collectors are stateless and thus many instances of Jaeger Collector can be
 |options:
   log-level:
 |Logging level for the collector.
-|`trace`, `debug`, `info`, `warning`, `error`, `fatal`, `panic`
+|Possible values: `debug`, `info`, `warning`, `error`, `fatal`, `panic`
 |===

modules/jaeger-config-query.adoc

@@ -40,7 +40,7 @@ Query is a service that retrieves traces from storage and hosts the user interfa
 |options:
   log-level:
 |Logging level for Query.
-|Possible values: `trace`, `debug`, `info`, `warning`, `error`, `fatal`, `panic`.
+|Possible values: `debug`, `info`, `warning`, `error`, `fatal`, `panic`.
 |
 
 |options: