November 30, 2011
Python agent v1.0.5.156
Importante
The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.
Fixes:
- Details of errors were not being captured and passed back to the core application to be displayed by the UI when the URL for the request had query string parameters. The problem was not causing failure of the overall web application but that a problem was occuring would have been identifiable though a Python agent exception and traceback being recorded in the Python agent log file with message:
- NameError: global name 'request_params' is not defined
- Slow transactions were never being recorded when agent run using method where no agent configuration file was being used. This is the case for example when using Heroku.
New features:
- Added support for the distributed task queuing system Celery. Tasks executed by a Celery server can be tracked and reported as background tasks against an application in the New Relic UI.
- Added support for tracking as external web service requests calls made out via the pywapi module.
- Added support for automatic wrapping of WSGI application entry point when using flup WSGI adapter for FASTCGI, SCGI and AJP.
- Added support for meinheld as standalone WSGI server and also as a worker class when using gunicorn.
- Added support for recording database transactions when using pyodbc.
November 15, 2011
Python agent v1.0.3.138
Importante
The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.
Fixes:
- Where instrumentation was not available for the web framework or toolkit being used and web transactions were being named according to the original URL, metric normalization rules were not being correctly applied when metric grouping issues occurred due to a large number of unique URLs. This was resulting in grouping of web transactions metrics under incorrect names leading to the data presented by the UI being unhelpful or misleading.
- Agent would fail when collecting WSGI hosting environment information when an older version of Tornado web server was used which did not provide version information. This would lead to no web transactions metrics being reported as failure occured when agent was trying to register with the New Relic core application.
- Instrumentation of the feedparser module was not catering for the fact that the parse() function could be supplied arguments beyond just the URL to be retreived. This would result in an exception and the web transaction always failing when such additional arguments were supplied.
- Instrumentation for Django was improved so that view handler function name was reported against a web transaction rather than URL when using Django static files mechanism.
- Instrumentation for Django was improved so that technical 404 and 500 response handler function name was used for web transaction when appropriate.
- Instrumentation for Django was improved to ensure that request middleware function name was always used for web transaction name when it returned a valid response.
Features changed:
- Attributes captured from WSGI request environment such as 'REQUEST_METHOD', 'HTTP_REFERER' and 'HTTP_USER_AGENT' are now shown under the 'Request environment' category in error details and slow transaction traces rather than under 'Custom parameters'.
- The HTTP response status for a web transaction is now shown as 'STATUS' under the 'Response properties' category in error details and slow transaction traces rather than under 'Custom parameters'.
November 14, 2011
Python agent v1.0.2.130
Importante
The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.
Notes
The first general release of the Python agent. If you are using an older BETA version of the Python agent you should upgrade as soon as possible as many outstanding issues were fixed leading up to this release. No change history for older versions will be made available.