End-of-life announcements
- Latest Dynatrace
- Reference
- 1-min read
General policy
To deliver a premium experience, Dynatrace evolves in step with the technology stacks we build on. When our partner vendors retire older components, we also phase them out so you receive the most secure and fully supported innovations.
We communicate these changes through two milestones that help you plan ahead:
End of Support (EoS)
- Last date on which Dynatrace provides bug fixes or security updates.
- After EoS, the component keeps running, but maintenance stops and support is best-effort only. Features will no longer be maintained, and no critical fixes will be deployed.
- Ongoing operation, and associated risk, becomes the customer’s responsibility.
End of Life (EoL)
- Latest date when Dynatrace disables, removes, or blocks the component, ending its useful operation.
- Upgrade paths remain open so you can migrate and continue getting full value from Dynatrace.
- Support tickets related to the component are no longer accepted.
Scheduled EOL for unsupported OneAgent versions
If you are running any of the OneAgent versions listed below, upgrade to a supported version before the EOL date to ensure uninterrupted monitoring.
| OneAgent versions | Standard EoS 1 | EoL |
|---|---|---|
1.141 and earlier | 2018 | Aug 1, 2025 |
1.215 and earlier | April 29, 2022 | Oct 1, 2025 |
1.241 and earlier | June 8, 2023 | Jan 1, 2026 |
1.299 and earlier | Sep 30, 2025 | Sep 1, 2026 |
Python Extension Framework 1.0
We’re moving away from the retired Python 3.5/3.8 runtimes to a current, fully supported Python version so your extensions stay secure and future-ready. This extension framework upgrade closes unpatched security gaps, gives you access to the latest libraries and performance gains, and ensures continued compatibility with upcoming Dynatrace features.
OneAgent extensions
OneAgent version 1.299 is the last release that support the Python Extensions 1.0 framework.
- EoS: Support (that is bug fixes, security updates) ended on Sep 30, 2025.
- Python Extension Framework 1.0 is EoS since Sep 1, 2024.
- To continue using extensions after the OneAgent version 1.299 EoL date, migrate to the new Extensions framework and update OneAgent to a supported version. See Migration guides for custom extensions 1.0
ActiveGate extensions
ActiveGate version 1.299 is the latest release that supports Python Extensions 1.0.
- EoS: Support (that is bug fixes, security updates) ended Sep 30, 2025.
- Python Extension framework 1.0 is EoS since Sep 1, 2024.
Migration guides for custom extensions 1.0
Migrate all Python extensions 1.0 to the new Extensions to maintain a secure, supported environment.
To remain supported, update your OneAgent to the latest version.
Native mobile applications for iOS and Android
As part of our ongoing commitment to delivering a streamlined and consistent user experience, Dynatrace is retiring its native mobile applications for iOS and Android. This change aligns with our strategy to provide a unified, responsive web interface and leverage modern, flexible notification channels.
Key dates
- Last app update: End of 2025
- Sunset date: June 30, 2026
- Support ends: June 30, 2026
What’s changing?
The Dynatrace native mobile apps will no longer be available for download or supported after the sunset date.
We encourage you to access Dynatrace via the responsive web interface, which offers full functionality across all device types and screen sizes.
Push notifications will now be delivered through third-party integrations such as Slack, Teams, PagerDuty, email, and ntfy.
Why this change?
- Unified experience: A single responsive web platform ensures consistent functionality across all devices.
- Flexibility: You can choose your preferred communication tools for alerts and updates.
Recommended actions
- Begin using the responsive web interface.
- Set up your preferred notification integrations via:
- Dynatrace SaaS: Workflows
- Dynatrace Managed: Problem notifications
- Remove the native app from your devices after the sunset date.
Need help?
For assistance with transitioning or setting up integrations, please see the Documentation links above or contact Support.
Legacy ActiveGate Update now action
The legacy, cron-based Update now action for Environment ActiveGate, which force-updates an ActiveGate immediately without version selection or update window support, is deprecated.
This action is superseded by Environment ActiveGate auto-update, which now supports selecting a target version and choosing an update mode, including scheduling updates to run only during configured update windows. See 
Fleet Management.
Key dates
- End of Life (EoL): January 1, 2027. The legacy Update now action and the
forceUpdateAPI flag are removed on this date.
What's changing?
- The Update now action (and the underlying
forceUpdateAPI flag) no longer receives feature investment. - Auto-update now supports selecting a target version and scheduling updates to run only during configured update windows, in addition to immediate, on-demand updates to the configured target version.
Recommended actions
- Configure a target version, update mode, and update windows for your Environment ActiveGates in Fleet Management.
Log Monitoring Classic
Log Monitoring Classic is being retired in favor of Log Management and Analytics powered by Grail, which stores your log data in Grail and lets you analyze it with DQL alongside metrics, traces, and events.
For the original announcement, see Log Monitoring Classic end-of-life in the Dynatrace SaaS 1.328 release notes.
Key dates
| Milestone | Date | What happens |
|---|---|---|
API deprecation | November 2025 | Three Log Monitoring API v2 endpoints are declared deprecated. |
Automatic upgrade of inactive environments | April 2026 | Environments that haven't ingested logs in the previous 90 days are automatically upgraded to Log Management and Analytics. Environments that are actively ingesting logs aren't affected at this stage. |
End of Life (EoL) | January 2027 | All remaining Dynatrace SaaS environments running Log Monitoring Classic are automatically upgraded to Log Management and Analytics. |
What's changing?
The following Log Monitoring API v2 endpoints are deprecated:
GET search logsGET export logsGET aggregate logs
After the upgrade, log data is stored in Grail and queried with DQL. Management zones don't apply to log data in Grail; access is controlled through buckets and policies instead.
Recommended actions
- Upgrade before the EOL date instead of waiting for the automatic upgrade, so you can choose the timing and keep existing log data. Follow Upgrade Log Monitoring Classic to Log Management and Analytics.
- If you're not sure whether your environment still runs Log Monitoring Classic, see Identify Logs Classic presence.
- Switch from the deprecated Log Monitoring API v2 endpoints to the Grail Query API.