This document gives more detail about the integration step of installing the Python agent.
For install instructions for the Python agent, see Standard install.
Overview of integration procedure
After you install the Python agent package and create a config file, the Python agent must be integrated with your application. This step allows the agent to capture and report your application's important functions and web requests.
There are two integration methods:
- Running the admin script via command line: This method is recommended because it is easy and doesn't require making changes to your app code.
- Manual integration: If, for whatever reason, you cannot use the admin script method, you can manually initialize the Python agent in your app code.
Admin script integration method
For a simple explanation of how to use the admin script via the command line, see the integration section of the advanced install instructions. Here are instructions with more details and context.
newrelic-admin admin script prefixes the command you use to start your WSGI server or web app. This script works by wrapping your startup command and listening for certain function classes used by common frameworks. (To instrument functions and methods that are not instrumented by default, you would use custom instrumentation.)
Here are examples of running the script:
|Old command form||New command form|
The following examples give instructions for a Bourne-style shell. You may need to adjust these instructions for a different shell.
- Gunicorn example
If you're using Gunicorn (a popular Python web server) and your startup command is:
gunicorn -w 3 wsgi:application
Then your new agent-integrated command would be:
NEW_RELIC_CONFIG_FILE=newrelic.ini newrelic-admin run-program gunicorn -w 3 wsgi:application
- uWSGI run directly on a WSGI application
newrelic-admin run-program uwsgi --socket /tmp/uwsgi.sock --single-interpreter --enable-threads wsgi.py
- Paster serve
Here's an example of running the admin script using paster serve on a WSGI app specified in a paster ini configuration file:
newrelic-admin run-program paster serve production.ini
For framework-specific documentation on using the admin script, see Web frameworks and servers.
Here are some advanced instructions for running the admin script:
- Splitting admin script command across multiple lines
You can separately set and export the
NEW_RELIC_CONFIG_FILEenvironment variable before running the script. Ensure you substitute your existing command options for
NEW_RELIC_CONFIG_FILE=newrelic.ini export NEW_RELIC_CONFIG_FILE newrelic-admin run-program YOUR_COMMAND_OPTIONS
If your startup command uses
exec, separate the setting of the environment variable from the execution of the admin script. Ensure you substitute your existing command options for
NEW_RELIC_CONFIG_FILE=newrelic.ini export NEW_RELIC_CONFIG_FILE exec newrelic-admin run-program YOUR_COMMAND_OPTIONS
If you use a process management system such as supervisord where the environment variables must be set in a separate configuration setting, you cannot set them on the same line as the command.
For example, under supervisord you might use this (ensure you substitute your existing command options for
[program:warpdrive] command = newrelic-admin run-program YOUR_COMMAND_OPTIONS environment = NEW_RELIC_CONFIG_FILE=newrelic.ini
- Running admin script with Python executable
If the command being run is the
pythonexecutable and it is being run directly on a Python code file as
python main.py, use either of the following:
newrelic-admin run-program python main.py newrelic-admin run-python main.py
run-pythonwill always use the same
pythonexecutable as is installed in the Python installation or virtual environment that newrelic-admin is installed.
- Notes about the location of newrelic-admin
The newrelic-admin program you run must be coming from the same Python installation or virtual environment as your application is using. You cannot mix programs/components from different Python installations. If this is done, the agent will not run correctly.
If you use a process management system such as supervisord in a virtual environment, you could use this configuration:
[program:warpdrive] command = newrelic-admin run-program
environment = PATH="/path/to/python/app/venv/bin",NEW_RELIC_CONFIG_FILE="newrelic.ini" directory = /path/to/python/app user = www-data
PATHenvironment variable that points to the same path that would be used by the virtual environment.
For more information on these options to newrelic-admin and the different configuration options based on user environment variables, see the more detailed documentation for the
For more information on using the admin script, see Admin script details.
Manual integration in app code
If you cannot use the recommended admin script integration method or don't wish to, you must initialize the Python agent manually in your web app code. This process involves importing a Python agent package into your app and making a call to initialize the agent. This call modifies your app's import mechanism so that when libraries are imported, the agent listens for the function classes it recognizes.
For manual integration, add the following to the beginning of the application script file or module that holds your WSGI entry point.
Unlike standard Python functionality, the import order matters: the agent package must be imported first.
import newrelic.agent newrelic.agent.initialize('/some/path/newrelic.ini') ... YOUR_OTHER_IMPORTS
In this example, /some/path/newrelic.ini represents the location of the copy of the config file created during Python agent installation. The config file must be readable by your web application.
For more on deployment environment overrides, select the following dropdown:
- Deployment environment overrides
To specify an override in the agent config file corresponding to a specific deployment environment, the name of that environment should be supplied as the second argument to the
import newrelic.agent newrelic.agent.initialize('/some/path/newrelic.ini', 'staging')
If you have installed the Python package into a Python virtual environment, the above lines must be added after you activated or otherwise have setup sys.path to find your virtual environment.
The above should, whenever possible, precede any imports for modules which are going to be instrumented. For some web frameworks, including Flask, this is mandatory. The instrumentation will not work correctly if not placed before all imports which cause code from that framework to be imported.
If you do not use the admin script, but still wish to use the environment variables
NEW_RELIC_ENVIRONMENTto configure the agent, you can call the
initialize()function with no arguments and they will be automatically consulted.
import newrelic.agent newrelic.agent.initialize()
Alternatively, you can set the
NEW_RELIC_APP_NAMEenvironment variables if the defaults for all other configuration settings are suitable.
Do note however that when using an embedded environment, such as Apache/mod_wsgi, you generally cannot rely on being able to derive configuration from environment variables. This is because in embedded systems, more often than not, you don't have a way of being able to set process environment variables which are in turn available to the WSGI script file.
For additional details see the documentation for the initialize() function.
Unsupported web frameworks
If you are using an unsupported web framework or are constructing a WSGI application using a WSGI component library such as Werkzeug or Paste, you may also need to manually wrap the WSGI application entry point. This would be in addition to doing one of the main integration methods (using the admin script, or manually initializing the Python agent).
If the WSGI application entry point is a function declared in the file itself, use a decorator:
@newrelic.agent.wsgi_application() def application(environ, start_response): ...
If the WSGI application entry point is a function or object imported from a different module, wrap it with a wrapper object:
import myapp application = myapp.WSGIHandler() application = newrelic.agent.WSGIApplicationWrapper(application)
If a supported web framework is being used, you might still use the decorator or wrapper explicitly if, for example, you were adding additional WSGI middleware around the supported web framework. This will ensure that execution of all WSGI middleware is also covered by the monitoring done by the agent.