Release notes for Dynatrace SaaS version 1.345 covering new features and changes across observability, security, and platform areas. Highlights include an OpenPipeline Inline lookup processor for enrichment without external systems, a Service backtrace modal for tracing database call chains, and a workflow template that alerts on critical GenAI vulnerabilities via Slack. Also introduced: a centralized Kubernetes tagging strategy, platform tokens as a replacement for access tokens, auto-update support for ActiveGate/OneAgent images from public registries, and cost allocation metadata for Grail lookup files. Notably, Dynatrace now rejects connections from OneAgent versions 1.215 and earlier, and the DT_TRACING_LINK_ID field is deprecated.
Table of contents
Enrich signals at ingest with the new Inline lookup processorFeature updatesBreaking changesFixes and maintenanceQuestions this post answers
Why is my OneAgent no longer connecting to Dynatrace after upgrading to SaaS 1.345?
Dynatrace SaaS 1.345 rejects connections from OneAgent versions 1.215 and earlier. Anyone running OneAgent 1.215 or older must upgrade to a supported version to avoid data loss and connectivity issues, and to regain access to security fixes and features unavailable in older OneAgent releases. Track backend platform upgrade requirements like this on daily.dev before they break your monitoring pipeline.
Should I migrate from Dynatrace access tokens to platform tokens?
Yes, Dynatrace recommends migrating from access tokens to platform tokens as soon as convenient, since platform tokens are the designated successor offering more secure, unified authentication. Existing access tokens still work for now but will eventually be removed from Dynatrace Operator, with advance notice to be given in future release notes. Developers planning token migrations follow infrastructure changes like this on daily.dev.
What Dynatrace field is deprecated in SaaS 1.345 for distributed tracing?
The Semantic Dictionary field DT_TRACING_LINK_ID is now deprecated in Dynatrace SaaS 1.345. This coincides with a change where Dynatrace links between subpaths are no longer persisted as span links, affecting how distributed tracing data is represented in the platform. Engineers tracking observability field deprecations rely on daily.dev to stay ahead of breaking changes.