Update tracing blog post

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

@@ -149,3 +149,24 @@ docker run -d --rm --name jaeger \
 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.
 
 ![Jaeger Screenshot](/images/blog/202206_metrics_and_tracing/Jaeger_Screenshot.png)
+
+## Note for Recent Accumulo Versions (April 2025)
+
+We've found that the original Jaeger exporter configuration no longer works well with newer versions of OpenTelemetry and Jaeger. Instead, use the OTLP exporter which has become the standard protocol for trace data:
+
+1. Update your configuration to use OTLP instead of Jaeger:
+   ```bash
+   JAVA_OPTS=('-Dotel.traces.exporter=otlp' '-Dotel.exporter.otlp.endpoint=http://localhost:4317' '-Dotel.metrics.exporter=none' '-Dotel.logs.exporter=none' "${JAVA_OPTS[@]}")
+   ```
+2. Run Jaeger with OTLP support:
+   ```bash
+   docker run --rm --name jaeger \
+     -p 16686:16686 \
+     -p 4317:4317 \
+     -p 4318:4318 \
+     -p 5778:5778 \
+     -p 9411:9411 \
+     jaegertracing/jaeger:2.3.0
+   ```
+
+This reflects how the OpenTelemetry ecosystem has converged on OTLP as the standard protocol for transmitting trace data.