On this page:
Python Agent Support
- The Python agent supports CPython 2.6, 2.7, 3.3, 3.4, 3.5, and 3.6.
- Any Linux distribution based on glibc 2.5+
- Alpine Linux uses musl_libc. See https://wiki.alpinelinux.org/wiki/Running_glibc_programs for guidance on installing our agent on Alpine Linux.
- Mac OS X 10.8+
Python Frameworks and Protocols
|Framework/Protocol||Version||Entry Point Type||Default Transaction Naming|
|WSGI||1.0||Python Web||First two segments of the URI|
|Tornado||3.2 - 4.5||Python Web||First two segments of the URI|
AppDynamics has tested the Python Agent on Tornado, Django, Flask, CherryPy, Bottle, and Pyramid.
You can configure the agent to instrument any WSGI-based application or framework as Python Web, including (but not limited to) those listed below.
At present, the Python agent fully supports exception detection in Django, Flask, CherryPy, Bottle, Pyramid, and Tornado frameworks. Other WSGI frameworks and custom WSGI applications may install exception handlers that effectively hide some exceptions from the agent. In such cases, the agent will only detect exceptions during exit calls, uncaught exceptions which are propagated to the WSGI server, and exceptions reported via the custom business transaction API.
Database Exit Points
|Supported Database Exit Points||Version|
HTTP Exit Points
|Supported HTTP Exit Points|
* The agent detects calls to any external library built on top of httplib. Therefore, backend calls to such services, such as boto, dropbox, python-twitter, etc. are detected and displayed as HTTP exit calls.
Cache Exit Points
Supported Cache Exit Points