From 591c03e08614bed4ce997449ecba6c0bfcd3733a Mon Sep 17 00:00:00 2001 From: seachen Date: Sat, 17 Jul 2021 10:03:43 +0800 Subject: [PATCH 1/2] docs/jaeger: add jaeger production configuration --- .../supported-tracing-backends/jaeger.md | 45 ++++++++++++++++++- 1 file changed, 43 insertions(+), 2 deletions(-) diff --git a/daprdocs/content/en/operations/monitoring/tracing/supported-tracing-backends/jaeger.md b/daprdocs/content/en/operations/monitoring/tracing/supported-tracing-backends/jaeger.md index 5698f430a..89c53a5d4 100644 --- a/daprdocs/content/en/operations/monitoring/tracing/supported-tracing-backends/jaeger.md +++ b/daprdocs/content/en/operations/monitoring/tracing/supported-tracing-backends/jaeger.md @@ -62,8 +62,12 @@ The following steps shows you how to configure Dapr to send distributed tracing ### Setup -First create the following YAML file to install Jaeger -* jaeger-operator.yaml +First create the following YAML file to install Jaeger, file name is `jaeger-operator.yaml` + +#### development/test configuration + +defaultly, allInOne uses memory as the backend storage. If you use the YAML configuration to deploy in production environment, it is dangerous!!! + ```yaml apiVersion: jaegertracing.io/v1 kind: "Jaeger" @@ -80,6 +84,43 @@ spec: base-path: /jaeger ``` +#### production configuration + +jaeger uses elasticsearch as the backend storage, you maybe create jaeger-secret to access elasticsearch server. see [Configuring and Deploying Jaeger](https://docs.openshift.com/container-platform/4.7/jaeger/jaeger_install/rhbjaeger-deploying.html) + +> kubectl create secret generic jaeger-secret --from-literal=ES_PASSWORD='xxx' --from-literal=ES_USERNAME='xxx' -n ${NAMESPACE} + +```yaml +apiVersion: jaegertracing.io/v1 +kind: "Jaeger" +metadata: + name: jaeger +spec: + strategy: production + query: + options: + log-level: info + query: + base-path: /jaeger + collector: + maxReplicas: 5 + resources: + limits: + cpu: 500m + memory: 516Mi + storage: + type: elasticsearch + esIndexCleaner: + enabled: false ## turn the job deployment on and off + numberOfDays: 7 ## number of days to wait before deleting a record + schedule: "55 23 * * *" ## cron expression for it to run + image: jaegertracing/jaeger-es-index-cleaner ## image of the job + secretName: jaeger-secret + options: + es: + server-urls: http://elasticsearch:9200 +``` + Now, use the above YAML file to install Jaeger ```bash # Install Jaeger From e0eebc95c806692b02b17c4bfa442427b31c4ae7 Mon Sep 17 00:00:00 2001 From: Mark Fussell Date: Thu, 22 Jul 2021 14:58:25 -0700 Subject: [PATCH 2/2] Update jaeger.md --- .../tracing/supported-tracing-backends/jaeger.md | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/daprdocs/content/en/operations/monitoring/tracing/supported-tracing-backends/jaeger.md b/daprdocs/content/en/operations/monitoring/tracing/supported-tracing-backends/jaeger.md index 89c53a5d4..3fc369216 100644 --- a/daprdocs/content/en/operations/monitoring/tracing/supported-tracing-backends/jaeger.md +++ b/daprdocs/content/en/operations/monitoring/tracing/supported-tracing-backends/jaeger.md @@ -7,16 +7,13 @@ description: "Set up Jaeger for distributed tracing" type: docs --- -Dapr currently supports the Zipkin protocol. Since Jaeger is -compatible with Zipkin, the Zipkin protocol can be used to talk to -Jaeger. +Dapr supports the Zipkin protocol. Since Jaeger is compatible with Zipkin, the Zipkin protocol can be used to communication with Jaeger. ## Configure self hosted mode ### Setup -The simplest way to start Jaeger is to use the pre-built all-in-one -Jaeger image published to DockerHub: +The simplest way to start Jaeger is to use the pre-built all-in-one Jaeger image published to DockerHub: ```bash docker run -d --name jaeger \ @@ -55,7 +52,7 @@ dapr run --app-id mynode --app-port 3000 node app.js --config config.yaml ``` ### Viewing Traces -To view traces, in your browser go to http://localhost:16686 and you will see the Jaeger UI. +To view traces, in your browser go to http://localhost:16686 to see the Jaeger UI. ## Configure Kubernetes The following steps shows you how to configure Dapr to send distributed tracing data to Jaeger running as a container in your Kubernetes cluster, how to view them. @@ -86,7 +83,7 @@ spec: #### production configuration -jaeger uses elasticsearch as the backend storage, you maybe create jaeger-secret to access elasticsearch server. see [Configuring and Deploying Jaeger](https://docs.openshift.com/container-platform/4.7/jaeger/jaeger_install/rhbjaeger-deploying.html) +Jaeger uses elasticsearch as the backend storage, you may need to a create jaeger-secret to access elasticsearch server. See [Configuring and Deploying Jaeger](https://docs.openshift.com/container-platform/4.7/jaeger/jaeger_install/rhbjaeger-deploying.html) > kubectl create secret generic jaeger-secret --from-literal=ES_PASSWORD='xxx' --from-literal=ES_USERNAME='xxx' -n ${NAMESPACE}