Skip to content

Commit fa61c2d

Browse files
burningionEmanuele Palazzetti
authored andcommitted
Add note about debug mode, and note for debugging in Kubernetes (#476)
1 parent 7321f1c commit fa61c2d

File tree

1 file changed

+11
-3
lines changed

1 file changed

+11
-3
lines changed

docs/index.rst

Lines changed: 11 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -61,10 +61,18 @@ Pass along command-line arguments as your program would normally expect them::
6161

6262
ddtrace-run gunicorn myapp.wsgi:application --max-requests 1000 --statsd-host localhost:8125
6363

64-
`For most users, this should be sufficient to see your application traces in Datadog.`
64+
*As long as your application isn't running in* ``DEBUG`` *mode, this should be enough to see your application traces in Datadog.*
6565

66-
`Please read on if you are curious about further configuration, or
67-
would rather set up Datadog Tracing explicitly in code.`
66+
If you're running in a Kubernetes cluster, and still don't see your traces, make sure your application has a route to the tracing Agent. An easy way to test this is with a::
67+
68+
69+
$ pip install ipython
70+
$ DATADOG_TRACE_DEBUG=true ddtrace-run ipython
71+
72+
Because iPython uses SQLite, it will be automatically instrumented, and your traces should be sent off. If there's an error, you'll see the message in the console, and can make changes as needed.
73+
74+
Please read on if you are curious about further configuration, or
75+
would rather set up Datadog Tracing explicitly in code.
6876

6977

7078
Instrumentation

0 commit comments

Comments
 (0)