Closed ConnectWise-Lalit closed 1 year ago
With gunicorn (or anything that spawn child processes) we are limited by the OneAgent for C/C++ architecture.
We can either instrument gunicorn (the parent process) OR the children (the actual app that handles the requests). Not both.
Most customers opt to instrument the children, gunicorn metrics (http request count per status for instance) can still be ingested via the OneAgent statsd listener, you just don't get the purepaths starting in gunicorn, which don't provide any extra value anyways.
Documentation about the architecture is here
Our Python Gunicorn service not getting autoinstrumented using autodynatrace
ENV variables are set as bellow
Also tried using setting -
ENV AUTODYNATRACE_INSTRUMENT_GUNICORN=True
- Didnot helped.Gunicorn library version used -
gunicorn[gevent]==20.0.4