| navigation_title | Breaking changes |
|---|
Before you upgrade, carefully review the Elastic APM RPython Agent breaking changes and take the necessary steps to mitigate any issues.
% To learn how to upgrade, check out .
% ## Next version [elastic-apm-python-agent-nextversion-breaking-changes] % Release date: Month day, year
% ::::{dropdown} Title of breaking change
% Description of the breaking change.
% For more information, check [PR #](PR link).
% Impact
Impact of the breaking change.
% Action
Steps for mitigating deprecation impact.
% ::::
Release date: July 11, 2025
- Python 3.6 and 3.7 support has been removed. For more information, check #2338 and #2340.
- OpenTracing integration has been removed. For more information, check #2342.
- Log shipping fron APM Python agent has been removed, included flask and Django integrations. For more information, check #2348, #2346 and #2345.
Release date: February 1, 2021
- Python 2.7 and 3.5 support has been deprecated. The Python agent now requires Python 3.6+. For more information, check #1021.
- No longer collecting body for
elasticsearch-pyupdate anddelete_by_query. For more information, check #1013. - Align
sanitize_field_namesconfig with the cross-agent spec. If you are using a non-defaultsanitize_field_names, surrounding each of your entries with stars (e.g.*secret*) will retain the old behavior. For more information, check #982. - Remove credit card sanitization for field values. This improves performance, and the security value of this check was dubious anyway. For more information, check #982.
- Remove HTTP querystring sanitization. This improves performance, and is meant to standardize behavior across the agents, as defined in #334. For more information, check #982.
- Remove
elasticapm.tag()(deprecated since 5.0.0). For more information, check #1034.