Extend distributed tracing documentation to web frameworks

Author: LotharSee

ddtrace/propagation/http.py

@@ -39,11 +39,11 @@ def extract(self, headers):
 
             from ddtrace.propagation.http import HTTPPropagator
 
-            def child_call(url, headers):
+            def my_controller(url, headers):
                 context = HTTPPropagator.extract(headers)
                 tracer.context_provider.activate(context)
 
-                with tracer.trace("child_span") as span:
+                with tracer.trace("my_controller") as span:
                     span.set_meta('http.url', url)
 
         :param dict headers: HTTP headers to extract tracing attributes.

docs/index.rst

@@ -272,13 +272,25 @@ Distributed Tracing
 
 To trace requests across hosts, the spans on the secondary hosts must be linked together by setting `trace_id`, `parent_id` and `sampling_priority`.
 
+- On the server side, it means to read propagated attributes and set them to the active tracing context.
+- On the client side, it means to propagate the attributes, commonly as a header/metadata.
+
 `ddtrace` already provides default propagators but you can also implement your own.
 
-HTTP
-~~~~
+Web frameworks
+~~~~~~~~~~~~~~
+
+Some web framework integrations support the distributed tracing out of the box, you just have to enable it.
+For that, refer to the configuration of the given integration.
+Supported web frameworks:
+
+- Django
+
+
+HTTP client/server
+~~~~~~~~~~~~~~~~~~
 
-The `HTTPPropagator` is already automatically used in our `aiohttp` integration. For the others, you can use
-it manually.
+You can use the `HTTPPropagator` manually when used with an HTTP client or if your web framework isn't supported.
 
 .. autoclass:: ddtrace.propagation.http.HTTPPropagator
     :members: