mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
47 lines
1.8 KiB
Plaintext
47 lines
1.8 KiB
Plaintext
////
|
|
This module is included in the following assemblies:
|
|
* service_mesh/v2x/ossm-observability.adoc
|
|
////
|
|
|
|
:_mod-docs-content-type: PROCEDURE
|
|
[id="ossm-config-external-jaeger_{context}"]
|
|
= Connecting an existing distributed tracing Jaeger instance
|
|
|
|
If you already have an existing {JaegerName} instance in {product-title}, you can configure your `ServiceMeshControlPlane` resource to use that instance for {DTShortName}.
|
|
|
|
[IMPORTANT]
|
|
====
|
|
Starting with {SMProductName} 2.5, {JaegerName} and {es-op} are deprecated and will be removed in a future release. Red{nbsp}Hat will provide bug fixes and support for these features during the current release lifecycle, but these features will no longer receive enhancements and will be removed. As an alternative to {JaegerName}, you can use {TempoName} instead.
|
|
====
|
|
|
|
.Prerequisites
|
|
|
|
* {DTProductName} instance installed and configured.
|
|
|
|
.Procedure
|
|
|
|
. In the {product-title} web console, click *Ecosystem* -> *Installed Operators*.
|
|
|
|
. Click the *Project* menu and select the project where you installed the {SMProductShortName} control plane, for example *istio-system*.
|
|
|
|
. Click the {SMProductName} Operator. In the *Istio Service Mesh Control Plane* column, click the name of your `ServiceMeshControlPlane` resource, for example `basic`.
|
|
|
|
. Add the name of your {JaegerShortName} instance to the `ServiceMeshControlPlane`.
|
|
+
|
|
.. Click the *YAML* tab.
|
|
+
|
|
.. Add the name of your {JaegerShortName} instance to `spec.addons.jaeger.name` in your `ServiceMeshControlPlane` resource. In the following example, `distr-tracing-production` is the name of the {JaegerShortName} instance.
|
|
+
|
|
.Example distributed tracing configuration
|
|
[source,yaml]
|
|
----
|
|
spec:
|
|
addons:
|
|
jaeger:
|
|
name: distr-tracing-production
|
|
----
|
|
+
|
|
.. Click *Save*.
|
|
|
|
. Click *Reload* to verify the `ServiceMeshControlPlane` resource was configured correctly.
|