Python agent release notesRSS

Notes

This release of the Python agent fixes a bug in the package version collector that disabled telemetry from being sent to New Relic in certain cases.

Install the agent using easy_install/pip/distribute via the Python Package Index or download it directly from the New Relic download site.

Bug fixes

• Fix agent crash when uploading package version info

  • Previously, if package versioning was a class property then the function itself was sent with the payload. This would then display the __repr__() of the versioning class in the environment stats. In v10.3.0, this task was tweaked and moved to the harvest cycle that caused a failure during the payload conversion to JSON and disabled the telemetry transmission. This release introduces logic to exclude invalid data types from the module payload.

Support statement

We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date.

See the New Relic Python agent EOL policy for information about agent releases and support dates.

Notes

This release of the Python agent adds support for Valkey, configuration via TOML file, protobuf v5 for infinite tracing, attaching custom attributes and labels to log events, and some minor cleanup of HTTPX instrumentation. HTTP/2 support was validated for Daphne, Hypercorn, and HTTPX. Module information is now collected periodically which fixes a bug where the CPU usage would spike on application startup.

The Python agent now allows you to opt-in to adding your custom tags (labels) to agent-forwarded logs. With custom tags on logs, platform engineers can easily filter, search, and correlate log data for faster and more efficient troubleshooting, improved performance, and optimized resource utilization. To learn more about this feature see the documentation.

Install the agent using easy_install/pip/distribute via the Python Package Index or download it directly from the New Relic download site.

New features

• Add support for Valkey

  • Add instrumentation for Valkey. Thanks @jairhenrique for the contribution!

• Add TOML configuration file support

  • Support to read TOML configuration is now available. Thanks @Tatsh for the contribution!

• Add infinite tracing pb2 file for protobuf v5

  • This adds an additional pb2 file used for infinite tracing that is compatible with protobuf v5.

• Add support for attaching custom attributes to logs

  • A new configuration option has been added called application_logging.forwarding.custom_attributes that will add custom attributes to all log events when set.

• Add support for attaching labels to log events

  • Labels as attributes can now be added to log events. When application_logging.forwarding.labels.enabled is set the values in labels will be added to all log events. Labels can be excluded by setting application_logging.forwarding.labels.exclude.

Enhancements

• Minor cleanup of HTTPX instrumentation

  • Some minor cleanup was done in the HTTPX instrumentation.

• Validate HTTP/2 support

  • Added tests to ensure HTTP/2 support for the following frameworks:
    • Daphne
    • Hypercorn
    • HTTPX

Bug fixes

• Collect module information from application periodically instead of at startup

  • Previously, the New Relic Python agent collected the application's module information all at once during startup. In some extreme cases this would cause a large spike in CPU usage. This enhancement allows the agent to do this incrementally throughout the application's operation, preventing potential memory spikes during agent startup.

Support statement

We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date.

See the New Relic Python agent EOL policy for information about agent releases and support dates.

Notes

This release of the Python agent adds a flag for the Azure init container operator.

Install the agent using easy_install/pip/distribute via the Python Package Index or download it directly from the New Relic download site.

New features

• Add Azure Init Container Operator Flag

  • New Relic can be integrated into applications hosted on Microsoft Azure, either directly, through an init container for Azure Container Apps, or a pre-build startup script for Microsoft Azure App Service. You can flag that this is the installation method used by setting the NEW_RELIC_AZURE_OPERATOR_ENABLED environment variable.

Support statement

We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date.

See the New Relic Python agent EOL policy for information about agent releases and support dates.

Notes

This release of the Python agent adds support for Python 3.13, adds a new Large Language Model (LLM) API, supports Docker ID parsing in Amazon ECS Fargate environments, and instruments a new Langchain vectorstore.

Install the agent using easy_install/pip/distribute via the Python Package Index or download it directly from the New Relic download site.

New features

• Add support for Python 3.13

  • The agent now supports applications running in Python 3.13.

• Add new LLM custom attribute context manager API

  • The agent now includes a new context manager API that adds custom attributes to LLM events generated from calls to LLMs in application code. For more information on usage, please see our API documentation.

• Add support for reporting of Amazon ECS Fargate Docker IDs

  • The agent now reports Docker IDs for containers running in ECS Fargate environments.

• Add instrumentation for SQLiteVec vectorstore in Langchain

  • The agent now instruments similarity_search for the SQLiteVec vectorstore.

Support statement

We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date.

See the New Relic Python agent EOL policy for information about agent releases and support dates.

Notes

This release of the Python agent drops support for Python 2.7 and adds the following:

• a Kafka server metric
• host and port attributes for memcache
• support for kafka-python-ng
• support for uvicorn_worker
• an environment variable for garbage collector (GC) runtime metrics
• automatic detection for the function signature in LangChain's similarity_search
• updated support for OpenAI's chat class
• a fix for a bug in gRPC's entity name detection
• a fix for transaction context propagation loss in LangChain in the case of a new thread
• parsing of the request and response when running OpenAI via LangChain
• a fix for pyscopg v3 API incompatibilities
• a fix that removes versioned logic in loguru instrumentation

Install the agent using easy_install/pip/distribute via the Python Package Index or download it directly from the New Relic download site.

Deprecations

• Remove Python 2.7 Support

  • Removes compatibility with Python 2.7. Also removes support for the following libraries that were only supported on Python 2.7:
    • umemcache
    • oursql
    • pywapi
    • Pylons
    • web2py
    • weberror

New features

• Add Kafka server metric

  • Adds a metric to capture the host and port information for Kafka entities on both consumers and producers. This metric allows the UI to link AWS information with AWS MSK entities in the service map.

• Add capturing of memcache host and port

  • Adds capturing of host and port info on the following memcache libraries: bmemcached, aiomcache, and pymemcache. This allows the UI to link AWS information with AWS memcache entities in the service map.

• Add support for kafka-python-ng

  • kafka-python has been released under a new name: kafka-python-ng. This continues to support kafka-python under the new package name.

• Add support for uvicorn_worker

  • uvicorn.workers has been moved to a separate package called uvicorn_worker. This checks for both names of the module when reporting dispatcher information.

• Automatically detect function signature in LangChain similarity_search

  • Automatically detect the function signature when wrapping similarity_search.

• Add environment variable for garbage collector runtime metrics

  • Garbage collector runtime metrics can now be enabled/disabled via the following environment variable: NEW_RELIC_GC_RUNTIME_METRICS_ENABLED.

Bug fixes

• Fix bug in gRPC entity name detection

  • Previously, the gRPC channel entity name was missing the first character(s) in specific cases. This bug has been fixed.

• Fix issue in LangChain where a thread is started and the transaction context is lost

  • Previously, when LangChain called certain chains, such as retrieval chains, LangChain started a thread that caused the transaction to be lost, resulting in broken instrumentation. This has been fixed so the transaction context is passed across threads and instrumentation still works for retrieval chains.

• Fix parsing of request and response when running OpenAI via LangChain

  • Previously, when running OpenAI via LangChain the request and response were a different format and were not being recorded. This issue has been fixed.

• Instrument new path to OpenAI chat completions class

  • OpenAI moved the ChatCompletions class to a different path which prevented the instrumentation from being applied. This has been fixed.

• Fix pyscopg v3 API incompatibilities

  • Expand DBAPI2 wrappers to allow arbitrary kwargs on executemany(). Upgrade psycopg v3 instrumentation to allow arbitrary kwargs on executemany(). Rename existing psycopg v3 wrapper arguments to match the upstream library's names for compatibility.

• Remove versioned logic in loguru instrumentation

  • Removed versioned logic in loguru instrumentation to fix a bug that occurred when the version was undeterminable.

Support statement

We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date.

See the New Relic Python agent EOL policy for information about agent releases and support dates.

Notes

This release of the Python agent adds the following:

• Support for boto3's upload_file command
• Support for newly added Redis commands
• AWS SQS information on spans
• server.address attribute on RabbitMQ

This release also fixes an issue with OpenAI's client instrumentation and missing parameters in Botocore SQS.

Install the agent using easy_install/pip/distribute via the Python Package Index or download it directly from the New Relic download site.

New features

• Add instrumentation for upload_file in boto3

  • Add instrumentation to the s3transfer BoundExecutor submit function, allowing the agent to support the upload_file operation in boto3.

• Add support for new Redis commands

  • Add instrumentation for the following commands in Redis:
    • hexpire
    • hexpireat
    • hexpiretime
    • hpersist
    • hpexpire
    • hpexpireat
    • hpexpiretime
    • hpttl
    • httl

• Capture AWS SQS information on message spans:

  • The Python Agent now captures the following AWS SQS information on message spans, allowing the UI to link AWS information with AWS SQS:
    • messaging.system - aws_sqs
    • cloud.region - AWS region
    • cloud.account.id - AWS account ID
    • messaging.destination.name - AWS queue name

• Add server.address attribute to RabbitMQ:

  • Add server.address attribute to RabbitMQ, allowing the UI to link AWS information with AWS MQ.

Bug fixes

• Fix TypeError in OpenAI instrumentation:

  • Newer versions of OpenAI include an additional argument, resulting in an error with the base client instrumentation. This has been fixed.

• Fix missing parameters in MessageTrace:

  • Resolved issue where parameters were not being passed from the MessageTraceWrapper to the MessageTrace.

Support statement

We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date.

See the New Relic Python agent EOL policy for information about agent releases and support dates.

Notes

This release of the Python agent adds instrumentation for aiomcache, support for an internally set collect_ai serverside configuration setting, formatting stack traces in NewRelicContextFormatter, fixes a crash in package catpuring in Python 2.7, an attribute check in OpenAI instrumentation, and casing on LangChain metric and span names.

Install the agent using easy_install/pip/distribute via the Python Package Index or download it directly from the New Relic download site.

New features

• Add instrumentation for aiomcache:

  • Add instrumentation support for aiomcache. Thank you Jair Henrique for the contribution!

• Add support for collect_ai serverside config:

  • Add support for an internally set collect_ai serverside configuration setting. Note this is returned in the connect response when a particular feature flag is set on an account.

• Adds support for formatting stack traces in NewRelicContextFormatter:

  • NewRelicContextFormatter now implements the format_exc_info class method that formats stack traces. Thank you Daniel Fritz for the contribution!

Bug fixes

• Fix crash in package capture in Python 2.7:

  • Previously, when capturing packages on Python 2.7 an UnboundLocalError would be raised. This has been fixed.

• Fix attribute check in OpenAI:

  • Fix a typo in an attribute check inside the OpenAI instrumentation. Thank you Liam Niehus-Staab for the contribution!

• Fix casing on LangChain metric and span names:

  • Previously, if LangChain was being used in combination with an unsupported Large Language Model library (aka not Bedrock or OpenAI) then the AI dashboard tab would not appear in the UI because the metric name was not cased correctly. This has been fixed and the Span names have been updated to match the casing of the metric name.

Support statement

We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date.

See the New Relic Python agent EOL policy for information about agent releases and support dates.

Notes

This release of the Python agent adds agent_language to lambda metadata, support for injecting the agent into Kubernetes, support for psycopg 3.0+, optimizes plugins list capturing, fixes the Large Language Model event duration units, a crash in ASGI when the Content-Length header is missing, a crash when using OpenAI's .with_raw_response. and .with_streaming_response..

Install the agent using easy_install/pip/distribute via the Python Package Index or download it directly from the New Relic download site.

New features

• Add agent_language to lambda metadata

  • Add agent_language to collected lambda metadata.

• Optimize plugins list capturing

  • Skip checking for a package version on newrelic hooks that we know do not have versions.

• Add support for injecting the agent into Kubernetes

  • Updates the bootstrap sitecustomize file to support injecting the agent into a Kubernetes cluster.
  • A full product for agent injection in Kubernetes will be coming soon in public preview.
  • A new informational only setting called k8s_operator.enabled (with NEW_RELIC_K8S_OPERATOR_ENABLED as an environment variable) was added, which is used to report when the agent is injected into a Kubernetes cluster. This setting does not enable/disable this function of the agent.

• Add support for psycopg 3.0+

  • New instrumentation for psycopg 3.0+ has been added, providing database tracing for both the Connection and AsyncConnection classes.

Bug fixes

• Fix Large Language Model event duration units

  • Previously, durations on LLM events were recorded in seconds which did not match some of the other language agents. This has been changed to be milliseconds.

• Fix crash when using OpenAI's .with_raw_response.

  • Previously, an exception would be raised inside the instrumentation when .with_raw_response. was used. This no longer happens, the instrumentation successfuly records LLM data when .with_raw_response. is used.

• Fix crash when using OpenAI's .with_streaming_response.

  • Previously, an exception would be raised inside the instrumentation when .with_streaming_response. was used. This no longer happens, the instrumentation is just skipped.

• Fix a crash in ASGI when the Content-Length header is missing

  • Previously, an exception would be raised inside the instrumentation that injects the browser agent when an ASGI response was missing the Content-Length header. This issue has been fixed.

Support statement

We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date.

See the New Relic Python agent EOL policy for information about agent releases and support dates.

Notes

This release of the Python agent:

• Adds instrumentation for AIOBotocore
• Adds support for Meta Llama3 and Mistral AI in Amazon Bedrock
• Fixes an error parsing issue in OpenAI
• Updates Loguru's instrumentation to use milliseconds instead of seconds

Install the agent using easy_install/pip/distribute via the Python Package Index or download it directly from the New Relic download site.

New features

• Add AIOBotocore instrumentation

  • Add instrumentation for AIOBotocore. Supports proxy mode in addition to standard operation.

• Add new Amazon Bedrock models

  • Add instrumentation for the following Amazon Bedrock models:
    • Meta Llama3
    • Mistral AI

Bug fixes

• Fix OpenAI error parsing

  • Previously, if an error in OpenAI was encountered, the Python Agent would attempt to override the default error.message within notice_error() with the one used in OpenAI. However, if there was no message attribute in the error, the Python Agent would crash. Now it defaults to the original methodology of error handling by the Python Agent.

• Record timing in Loguru in milliseconds

  • Timing in Loguru is recorded as an integer and if that value was less than 1 second, it would record it as 0s. This changes the units to be in milliseconds instead. Thanks, (@julia-tadej-wwtech)[https://github.com/julia-tadej-wttech] for the contribution!

Support statement

We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date.

See the New Relic Python agent EOL policy for information about agent releases and support dates.