|
1 | 1 | """ |
2 | | -The Django integration will trace requests, database calls and template |
3 | | -renderers. |
| 2 | +The Django integration will trace users requests, template renderers, database and cache |
| 3 | +calls. |
4 | 4 |
|
5 | 5 | To enable the Django integration, add the application to your installed |
6 | | -apps and our tracing middleware **as a first middleware** in your ``MIDDLEWARE`` |
7 | | -list, as follows:: |
| 6 | +apps, as follows:: |
8 | 7 |
|
9 | 8 | INSTALLED_APPS = [ |
10 | 9 | # your Django apps... |
|
21 | 20 | 'TAGS': {'env': 'production'}, |
22 | 21 | } |
23 | 22 |
|
24 | | -If you need to access to integration settings, you should:: |
| 23 | +If you need to access to Datadog settings, you can:: |
25 | 24 |
|
26 | 25 | from ddtrace.contrib.django.conf import settings |
27 | 26 |
|
|
45 | 44 | are sent to the trace agent. This setting cannot be changed at runtime |
46 | 45 | and a restart is required. By default the tracer is disabled when in ``DEBUG`` |
47 | 46 | mode, enabled otherwise. |
| 47 | +* ``AGENT_HOSTNAME`` (default: ``localhost``): define the hostname of the trace agent. |
| 48 | +* ``AGENT_PORT`` (default: ``8126``): define the port of the trace agent. |
48 | 49 | * ``AUTO_INSTRUMENT`` (default: ``True``): if set to false the code will not be |
49 | 50 | instrumented (even if ``INSTRUMENT_DATABASE``, ``INSTRUMENT_CACHE`` or |
50 | 51 | ``INSTRUMENT_TEMPLATE`` are set to ``True``), while the tracer may be active |
|
58 | 59 | * ``INSTRUMENT_TEMPLATE`` (default: ``True``): if set to ``False`` template |
59 | 60 | rendering will not be instrumented. Only configurable when ``AUTO_INSTRUMENT`` |
60 | 61 | is set to ``True``. |
61 | | -* ``AGENT_HOSTNAME`` (default: ``localhost``): define the hostname of the trace agent. |
62 | | -* ``AGENT_PORT`` (default: ``8126``): define the port of the trace agent. |
63 | 62 | """ |
64 | 63 | from ..util import require_modules |
65 | 64 |
|
|
0 commit comments