apiVersion: jaegertracing.io/v1
kind: Jaeger
metadata:
name: jaeger
namespace: default
Using Jaeger with OpenShift Serverless allows you to enable distributed tracing for your serverless applications on OpenShift Container Platform.
To configure Jaeger for use with OpenShift Serverless, you will need:
Cluster administrator permissions on an OpenShift Container Platform cluster.
A current installation of OpenShift Serverless Operator and Knative Serving.
A current installation of the Jaeger Operator.
Create and apply a Jaeger custom resource YAML file that contains the following sample YAML:
apiVersion: jaegertracing.io/v1
kind: Jaeger
metadata:
name: jaeger
namespace: defaultEnable tracing for Knative Serving, by editing the KnativeServing resource and adding a YAML configuration for tracing.
apiVersion: operator.knative.dev/v1alpha1
kind: KnativeServing
metadata:
name: knative-serving
namespace: knative-serving
spec:
config:
tracing:
sample-rate: "0.1" (1)
backend: zipkin (2)
zipkin-endpoint: http://jaeger-collector.default.svc.cluster.local:9411/api/v2/spans (3)
debug: "false" (4)| 1 | The sample-rate defines sampling probability. Using sample-rate: "0.1" means that 1 in 10 traces will be sampled. |
| 2 | backend must be set to zipkin. |
| 3 | The zipkin-endpoint must point to your jaeger-collector service endpoint. To get this endpoint, substitute the namespace where the Jaeger custom resource is applied. |
| 4 | Debugging should be set to false. Enabling debug mode by setting debug: "true" allows all spans to be sent to the server, bypassing sampling. |
Access the Jaeger web console to see tracing data. You can access the Jaeger web console by using the jaeger route.
Get the jaeger route’s hostname by entering the following command:
$ oc get route jaegerNAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD
jaeger jaeger-default.apps.example.com jaeger-query <all> reencrypt NoneOpen the endpoint address in your browser to view the console.