This release of the Python agent adds much more flexibility around what attributes are sent to New Relic, and where they are displayed.
For a list of known issues with the Python agent, see Status of the Python agent.
- Flexible capturing of attributes
Attributes are key-value pairs that contain additional information to be added to an event or transaction. These key-value pairs can be viewed within transaction traces in New Relic APM, traced errors in New Relic APM, transaction events in Insights, and page views in Insights.
A number of new configuration settings have been introduced to allow you to customize exactly which attributes will be sent to each of these destinations.
For details, see Python agent attributes.
Several configuration settings have been deprecated. The most commonly used of the deprecated settings are
ignored_params. It is still possible to achieve the same functionality as the old settings by using the new
attributes.exclude settings. For examples, see Python agent attribute examples.
A complete list of deprecated settings can be found in deprecated configuration settings.
While the usage of deprecated settings is still supported, we recommend upgrading your configuration to use the new settings as soon as possible.
Previously, it was possible to save a list, dict, or tuple as an attribute value that could be displayed in transaction and error traces. However, these same attributes could not be displayed in Insights events. Now, all attributes are handled in a consistent manner, which means that all attribute values must be one of the following types:
Python 2: str, unicode, int, long, float, bool Python 3: str, bytes, int, float, bool
All values which are not one of these types are automatically converted by calling