This release of the Python agent provides support for Labels and Rollups, making it possible to organize your applications in the APM UI into meaningful categories.
For a list of known issues with the Python agent see Status of the Python agent.
Labels and Rollups
The Python agent now supports the ability to apply labels to applications, so that you can easily sort, filter, and page through all of the applications on your account's Applications list.
Configuration can be done in the newrelic.ini file:
labels = Server:One;Data Center:Primary
Labels can also be configured by setting a
NEW_RELIC_LABELS=Server:One;Data Center:PrimaryMore information on using labels to categorize your applications can be found in the New Relic APM documentation.
New CPU Reporting in Environment Snapshot
Previously, the Python agent captured two CPU-related values to report to the Environment Snapshot: Logical Processors and Physical Processors. Now, it captures the following three values:
- Logical Processors: The total number of hyper-threaded execution contexts available, including execution contexts that may exist on the same core. This value remains unchanged from previous agents.
- Physical Cores: The total number of physical CPU cores available, counting hyper-threaded siblings as a single core. This value was previously reported as "Physical Processors."
- Physical Processor Packages: The total number of processor packages or dies (each of which may contain multiple physical cores). This value is new with this agent release.
A "Runtime Error: transaction already active" will no longer be seen in the case where the agent created nested transaction wrappers and
newrelic.agent.ignore_transaction()was called within the outer wrapper but outside the inner wrapper. Previously, this error could have also been triggered when using the WSGI environment setting for
newrelic.ignore_transactionset by SetEnv in mod_wsgi.
Prior to this version, the HTTP_REFERER URL reported for a transaction contained query parameters, even if the
capture_paramssetting was set to False. Now, the
capture_paramssetting is respected when reporting the HTTP_REFERER URL.