diff --git a/tracing.md b/tracing.md
index f8087d33ee8..80b037d262f 100644
--- a/tracing.md
+++ b/tracing.md
@@ -24,14 +24,24 @@ to get started:
       -p 9411:9411 \
       jaegertracing/all-in-one:1.17
     ```
-2. Every single oCIS service has its own environment variables for enabling and configuring tracing. You can, for example,
-enable tracing in Reva when starting the oCIS single binary like this:
-    ```console
-    REVA_TRACING_ENABLED=true \
-    REVA_TRACING_ENDPOINT=localhost:6831 \
-    REVA_TRACING_COLLECTOR=http://localhost:14268/api/traces \
-    ./bin/ocis server
-    ```
+2. Every single oCIS service has its own environment variables for enabling and configuring tracing.
+    1. You can enable and configure tracing on each service individually. For example, enable tracing
+        in Reva when starting the oCIS single binary like this:
+        ```console
+        REVA_TRACING_ENABLED=true \
+        REVA_TRACING_ENDPOINT=localhost:6831 \
+        REVA_TRACING_COLLECTOR=http://localhost:14268/api/traces \
+        ./bin/ocis server
+        ```
+    2. Enabling and configuring tracing on oCIS itself will forward the configuration to all services:
+        ```console
+        OCIS_TRACING_ENABLED=true \
+        OCIS_TRACING_ENDPOINT=localhost:6831 \
+        OCIS_TRACING_COLLECTOR=http://localhost:14268/api/traces \
+        ./bin/ocis server
+        ```
+       If you want to set individual tracing configuration for each service, make sure to set
+       `OCIS_TRACING_ENABLED=false`.
 3. Make the actual request that you want to trace.
 4. Open up the [Jaeger UI](http://localhost:16686) to analyze request traces.