Skip to content

Commit 62573fc

Browse files
Update tracing blog post to remove the instructions to set the client property (#469)
* Update tracing blog post to remove the instructions to set the client property Removed step 4 under the Tracing Example as setting that property does nothing anymore. --------- Co-authored-by: Dom Garguilo <domgarguilo@apache.org>
1 parent 5faf42a commit 62573fc

1 file changed

Lines changed: 6 additions & 12 deletions

File tree

_posts/blog/2022-06-22-2.1.0-metrics-and-tracing.md

Lines changed: 6 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -114,15 +114,9 @@ This example uses the OpenTelemetry Java Agent jar file to configure and export
114114
general.opentelemetry.enabled=true
115115
```
116116

117-
4. To enable tracing in the shell, set the `general.opentelemetry.enabled` property in the accumulo-client.properties configuration file.
118-
```
119-
# OpenTelemetry settings
120-
general.opentelemetry.enabled=true
121-
```
122-
123-
**Note:** If you are using Accumulo 2.1.4 or newer, skip steps 5-6 below and follow the updated instructions in the [Updated Configuration with Newer Versions of OpenTelemetry](#updated-configuration-with-newer-versions-of-opentelemetry) section.
117+
**Note:** If you are using Accumulo 2.1.4 or newer, skip steps 4-5 below and follow the updated instructions in the [Updated Configuration with Newer Versions of OpenTelemetry](#updated-configuration-with-newer-versions-of-opentelemetry) section.
124118

125-
5. Configure the OpenTelemetry JavaAgent in accumulo-env.sh by uncommenting the following and updating the path to the java agent jar:
119+
4. Configure the OpenTelemetry JavaAgent in accumulo-env.sh by uncommenting the following and updating the path to the java agent jar:
126120
```
127121
## Optionally setup OpenTelemetry SDK AutoConfigure
128122
## See https://github.com/open-telemetry/opentelemetry-java/tree/main/sdk-extensions/autoconfigure
@@ -132,7 +126,7 @@ general.opentelemetry.enabled=true
132126
#JAVA_OPTS=('-javaagent:path/to/opentelemetry-javaagent.jar' "${JAVA_OPTS[@]}")
133127
```
134128

135-
6. Start Jaeger Docker container
129+
5. Start Jaeger Docker container
136130
```
137131
docker run -d --rm --name jaeger \
138132
-e COLLECTOR_ZIPKIN_HOST_PORT=:9411 \
@@ -145,12 +139,12 @@ docker run -d --rm --name jaeger \
145139
-p 14250:14250 \
146140
-p 9411:9411 jaegertracing/all-in-one:1.35
147141
```
148-
7. Start Accumulo. You should see the following statement in the server log files
142+
6. Start Accumulo. You should see the following statement in the server log files
149143
```
150144
[trace.TraceUtil] INFO : Trace enabled in Accumulo: yes, OpenTelemetry instance: class io.opentelemetry.javaagent.instrumentation.opentelemetryapi.v1_10.ApplicationOpenTelemetry110, Tracer instance: class io.opentelemetry.javaagent.instrumentation.opentelemetryapi.trace.ApplicationTracer
151145
```
152146

153-
8. View traces in Jaeger UI at http://localhost:16686. You can select the service name on the left panel and click `Find Traces` to view the trace information. If everything is working correctly, then you should see something like the image below.
147+
7. View traces in Jaeger UI at http://localhost:16686. You can select the service name on the left panel and click `Find Traces` to view the trace information. If everything is working correctly, then you should see something like the image below.
154148

155149
<a class="p-3 border rounded d-block" href="{{ site.baseurl }}/images/blog/202206_metrics_and_tracing/Jaeger_Screenshot.png">
156150
<img src="{{ site.baseurl }}/images/blog/202206_metrics_and_tracing/Jaeger_Screenshot.png" class="img-fluid rounded" alt="Jaeger Screenshot"/>
@@ -160,7 +154,7 @@ docker run -d --rm --name jaeger \
160154

161155
The original tracing example above was written for Accumulo 2.1.0 which uses OpenTelemetry 1.19.0. Accumulo 2.1.4 has been updated to use OpenTelemetry 1.48.0, which requires different configuration. When working with Accumulo 2.1.4 or any deployment using OpenTelemetry 1.48.0 or newer, use OTLP (OpenTelemetry Protocol) instead of the direct Jaeger exporter.
162156

163-
Follow steps 1–4 from the [Tracing Example](#tracing-example) section, then use these updated steps in place of steps 5-6:
157+
Follow steps 1–3 from the [Tracing Example](#tracing-example) section, then use these updated steps in place of steps 4-5:
164158

165159
1. Configure the OpenTelemetry JavaAgent in accumulo-env.sh with OTLP export:
166160
```bash

0 commit comments

Comments
 (0)