What's new in Dynatrace SaaS 1.350
- Release notes
- 18-min read
- Rollout start on Nov 4, 2026
This page showcases new features, changes, and bug fixes in Dynatrace SaaS version 1.350. It contains:
Platform | Dashboards
Create a PDF report from any dashboard
You can export an entire dashboard as a PDF. At the top of any dashboard, open the menu next to the dashboard title and select Print view. This functionality is available only in Chromium-based browsers, such as Chrome or Edge.
Platform | Dynatrace Intelligence
Ask Dynatrace Assist about library vulnerabilities from the vulnerability feed
Use Dynatrace Assist, or your AI agent using the Dynatrace MCP server, to analyze whether a CVE affects your libraries, which version fixes it, and whether it is exploited in the wild (CISA KEV). Answers combine the Dynatrace Vulnerability Feed with your runtime data, so you know which open vulnerabilities to fix first.
The feed covers vulnerabilities in libraries across npm, PyPI, Maven, Packagist, Go, and NuGet.
Feature updates
Application Observability
Analyze all trace entry points in Distributed Tracing unified view
Distributed Tracing now shows all trace entry points in a unified Transactions view, replacing the former Requests perspective.
Transactions covers three types in a single list:
- HTTP endpoint requests
- Message processing events (queues and topics)
- Serverless invocations (AWS Lambda, Azure Functions)
The name column adapts per type, showing the endpoint name, messaging destination, or function name as appropriate.
Failure Analysis and Response Time Analysis in 
Services apply the same model, extending coverage beyond HTTP endpoints to all transaction types. Existing usage of request.* attributes continues to work alongside the new model. For the full list of transaction attributes, see the Semantic Dictionary.
Application Observability | Distributed Tracing
Go static monitoring no longer requires ptrace on Linux
Go static monitoring no longer requires the Linux ptrace capability. This improvement is planned to replace the existing opt-in OneAgent feature Go improved static monitoring.
Application Observability | Distributed Tracing
Find and filter fields by technical key or display name in Distributed Tracing
Fields in Distributed Tracing now show their display names from the semantic dictionary. If a field has no display name, the app shows its key.
- Keys in the filter bar. The filter bar always shows the technical key that it filters on. If the Dynatrace semantic dictionary defines a display name, the auto-complete list shows it too, and you can use it.
- Field details on hover. Hover over a field in a table header, in the facets, or in the span details to see its technical key, display name, and a detailed description from the semantic dictionary.
- Your choice of names. Open App settings to choose whether the app shows display names or technical keys.
Application Observability | Log Analytics
New Share button in the header copies a link to your current Logs view
A new Share button in the header copies a link to your current Logs view, including query, filters, segment, timeframe, and more.
Application Observability | Services
Database query response time and error metrics for services
Services now record dt.service.database.query.response_time and dt.service.database.query.error_count in addition to the existing query count, so you can spot slow or failing database calls without searching through traces. Both metrics have the same splittings as the query count and your primary tags, so you can chart, alert on, and segment database health by team, application, or environment.
Cost Intelligence
Cost Allocation for Real User Monitoring on the environment level
The Cost Allocation Extended Dashboard in the Dynatrace Community now shows Real User Monitoring usage per cost center, per product, or both. For more information, see Configure user-based Cost Allocation for queries, Automation Workflow, and Agentic AppEngine.
Data Observability
Pipeline events in definity extension
For the definity extension:
- Pipeline failure and degradation events are reported as Davis Problems, enabling proactive alerting and root-cause analysis
- The new definity Pipeline Events dashboard displays active/closed events and trends
- Problem categories and severities can be customized per event type in the extension configuration settings
Digital Experience | Synthetic
Shadow DOM support
The recorder now supports shadow DOM interactions.
- Records clicks and keystrokes inside shadow roots
- Generates DOM locators that traverse shadow boundaries
- Provides multiple fallback locators for playback reliability
- Events correctly propagate across shadow boundaries during playback
- Player changes (new events handling API) can be reverted by setting the experimental property
shouldUseLegacyEventstotrue
Limitations
- Maximum 15 nested shadow boundaries
- Closed shadow roots record the host element only
- iframes inside shadow roots are not supported
Infrastructure Observability
Infrastructure findings in QuickStart
New to Dynatrace? 
QuickStart helps you get started fast.
- One map for your whole environment. See Kubernetes clusters, cloud accounts, and hosts together, with the services that run on each one.
- Pick a node, get the answer. Select a cluster, AWS account, or host to see its charts and top findings, such as logs, CPU and memory slack, the top erroneous Lambda, and the busiest processes.
- Go deeper in one click. Select View cluster, View cloud, or View host to open the full details in a new tab. No configuration needed.
Try it now. Open QuickStart, select a cluster, cloud account, or host, and see what needs your attention.
Infrastructure Observability
More focused root cause analysis through automatic correlation of availability and shared disk events into single problems
Infrastructure & Operations now correlates:
- Availability events across affected hosts into a single problem. This reduces alert flood for IT teams and gives the right foundation for faster root cause analysis.
- Disk threshold events across hosts sharing a common disk into a single problem. This makes the shared disk visible as the focal point for investigation.
Infrastructure Observability | Clouds
Explore logs in context faster in 
Clouds
The Logs tab in Clouds now includes several improvements to help you explore logs faster, without leaving the app.
- Quick filter by status: Filter logs by status directly in context, with no need to run additional queries in
Logs. - Up to 1,000 log records: See a broader set of logs right where you are, without switching apps.
- Faster drill-downs: Navigate directly from in-context logs to related entities, traces, and user sessions for quicker root cause analysis.
Infrastructure Observability | Databases
Explore logs in context faster in 
Databases
The Logs tab in Databases now includes several improvements to help you explore logs faster, without leaving the app.
- Quick filter by status: Filter logs by status directly in context, with no need to run additional queries in Logs.
- Up to 1,000 log records: See a broader set of logs right where you are, without switching apps.
- Faster drill-downs: Navigate directly from in-context logs to related entities, traces, and user sessions for quicker root cause analysis.
Infrastructure Observability | Extensions
New Fortinet FortiManager extension available
Observe FortiManager managed devices, config sync, policy packages, and tasks. See Dynatrace Hub for details.
Infrastructure Observability | Infrastructure & Operations
Explore logs in context faster in Infrastructure & Operations
The Logs tab in Infrastructure & Operations now includes several improvements to help you explore logs faster, without leaving the app.
- Quick filter by log sources and status: Filter logs by log sources and status directly in context, with no need to run additional queries in Logs for basic filtering.
- Up to 1,000 log records included at no query cost: See a broader set of logs right where you are, without switching apps.
- Faster drill-downs: Navigate directly from in-context logs to related entities, traces, and user sessions for quicker root cause analysis.
Infrastructure Observability | Kubernetes
New ip attribute for the K8S_SERVICE Smartscape node
The K8S_SERVICE Smartscape node now has an ip attribute.
Infrastructure Observability | Kubernetes
Explore logs in context faster in 
Kubernetes
The Logs tab in Kubernetes now includes several improvements to help you explore logs faster, without leaving your current context.
- Kubernetes-aware log chart and filters: The log chart can now be split by Kubernetes topology. At the cluster level, you can instantly see which namespaces generate the most logs and filter down to a specific namespace with a single click.
- Up to 1,000 log records included at no query cost: See a broader set of logs right where you are, without switching apps or running additional queries.
- Faster drill-downs: Navigate directly from in-context logs to related entities, distributed traces, and user sessions for quicker root cause analysis.
Platform
Suppress problems during maintenance windows
You can now suppress problems for a specific maintenance window. During an active window, Dynatrace skips problem creation for the entities in the window's scope, so planned deployments, upgrades, and load tests no longer flood 
Problems with expected alerts that you have to filter out by hand.
Suppression is a per-window choice. When you create a maintenance window, or while it is still scheduled for the future, turn on problem suppression under Scope > Data scope.
Platform
Expanded auto-update support for public registry images
Dynatrace Operator now automatically resolves and updates container images for Dynatrace Kubernetes Node Configuration Collector, Dynatrace OTel Collector, and EdgeConnect, bringing the same seamless update experience to the full set of Dynatrace Operator-managed components.
Supported public registries offer multi-arch images adhering to best practices for immutability and signing to strengthen supply chain security.
For configuration details and more, see Use a public registry.
Platform | Dashboards
Reuse DQL across tiles with base queries in dashboards
Dashboards now let you define base queries centrally and reference them across multiple tiles, eliminating the need to copy and paste the same DQL into every tile that operates on the same data. Tiles on the dashboard can then reference the base query and extend it with their own filters or transformations. Dashboard variables work inside shared queries just as they do in annotations. If a referenced query is deleted or broken, only its dependent tiles are affected; the rest of the dashboard continues to render normally.
- To create a base query in the displayed dashboard, select Add > Base query and enter the DQL for the base query. This part runs first in every tile that references it.
- To use a base query in the displayed dashboard, edit a DQL tile on the dashboard, select Add base query, and select the base query. When this tile is evaluated, the base query DQL and the DQL in this tile are combined.
Platform | Dashboards
Bring structure to dashboards with collapsible rows
You can now organize dashboard tiles into named, collapsible rows. Give each row a title, an optional description, and a color, then collapse the sections you don't need. Tiles in a collapsed row skip their queries, which reduces load time and query cost.
Platform | Dynatrace Intelligence
Dynatrace Assist can now read environment configuration and content
Ask Dynatrace Assist about your environment’s setup and content. Assist can now read settings, dashboards, notebooks, segments, lookup tables, and much more, giving you much of what the Dynatrace CLI (dtctl) offers, directly in Assist.
Access is read-only and respects your existing permissions.
Platform | Notebooks
Validate notebooks with new app function and skill
Starting with Dynatrace version 1.350, Dynatrace provides an app function that validates notebooks. AI agents can use it to check a notebook before uploading it to the document store.
Skills shipped with the app
/skills/create-notebook/references/notebook-schema.md: A skill document to extend the context of Dynatrace Intelligence/skills/create-notebook/SKILL.md: A skill document to extend the context of Dynatrace Intelligence
App function shipped with the app
api/validate-notebook- Request:
{ document: json-object } - Response:
{ success: true; document: Notebook } | { success: false; error: ValidationFailure }
Platform | OneAgent
Log module CPU usage limit
The OneAgent Log module now supports a configurable CPU usage cap on Linux hosts.
- The limit is set as a percentage of total host CPU.
- You can apply the limit at the environment, host group, or host level.
- You don't need to restart OneAgent for the changes to apply.
When the cap is reached, the log module scales back the processing to stay within the boundary.
This setting is available for environments with constrained CPU headroom that require additional resource guardrails.
Platform | OneAgent
OneAgent on a host API auto-update request validation improved
The OneAgent on a host API now validates the requested version more strictly on PUT /hosts/{id}/autoupdate and POST /hosts/{id}/autoupdate/validator.
The API accepts only versions higher than the installed one. Lower or equal versions return 400 Bad Request with a constraintViolations message that shows both versions.
Platform | OpenPipeline
OpenPipeline data forwarding now supports additional event types
OpenPipeline data forwarding now supports additional event types: events, events.sdlc, security events, system events, business events (bizevents), Davis events (alerts), and Davis problems. You can forward these data types, unprocessed or processed, to your configured cloud object storage (AWS S3, Azure Blob Storage, or GCP Cloud Storage) for compliance, auditing, or external system integration.
Platform | OpenPipeline
More reliable automatic trace_id and span_id enrichment
OpenPipeline now handles logs ingested through AWS Firehose channels that carry both Dynatrace and AWS X-Ray trace and span identifiers in the content field.
Platform | Platform Services
Send Event to PagerDuty action in 
Workflows
Workflows now includes a Send Event to PagerDuty action that maps Dynatrace problem data to the PagerDuty Events V2 API. Based on that data, the action triggers a new alert or resolves an existing one in PagerDuty. A ready-to-use workflow template helps you get started quickly.
Platform | Platform Services
Mark documents as favorites in 
Dashboards and 
Notebooks
You can now mark any document as a favorite directly from the documents list or the documents sidebar in Dashboards and Notebooks. We also added favorite support to the documents API and the documents library, so you can programmatically mark documents as important and surface them in your own workflows.
Platform | Segments
Find segments faster with tabs
Segments are now easier to find with category tabs (All, Owned by me, Shared, and Ready-made) in 
Segments.
Platform | Smartscape
Scope Smartscape read access by node type
The storage:smartscape:read permission now supports storage:type as a condition field, letting administrators scope Smartscape node access by node type. The storage:type condition supports the =, IN, startsWith, and MATCH operators and accepts any Smartscape node type value in UPPERCASE_UNDERSCORE format.
Example: Grant access to all Synthetic location nodes by type:
ALLOW storage:smartscape:read WHERE storage:type = "SYNTHETIC_LOCATION";
Platform | Workflows
Workflows and ServiceNow Connector: Send Dynatrace problems to ServiceNow ITOM
ServiceNow Connector now includes the Send ITOM Event workflow action. Use it to send Dynatrace problems to ServiceNow IT Operations Management (ITOM) as events. A ready-made workflow template, Send problem as ITOM event to ServiceNow, helps you get started.
The template creates a ServiceNow alert when a problem opens and closes that alert when the problem closes. By default, it waits for root cause analysis and forwards problems with severity 1 to 3, plus problems without a severity. ServiceNow uses the root cause or first affected entity to find the matching configuration item (CI). Each alert includes tags and a link back to the problem in Dynatrace. You can fine-tune the field mappings to fit your ServiceNow setup.
Platform | Workflows
Create, read, update, and delete documents in workflows
Workflows now includes actions to create, read, update, and delete documents.
Breaking changes
Application Security
Prepare for SaaS 1.353 security event changes in OpenPipeline and retention
With Dynatrace SaaS version 1.353, planned for December 2026, security events become fully configurable in OpenPipeline, and security event storage consolidates into a single Grail bucket with a new default retention period. Most environments need no action, but check your queries and your retention needs before this release lands.
What you get:
Built-in security events are usable in OpenPipeline. From Dynatrace version 1.353, you can configure them exactly as you configure events, logs, and traces:
- Processing rules: add, enrich, or transform fields on ingest
- Metric extraction: define streaming metrics from findings data without scheduled DQL
- Access control: record-level access control with
dt.security_contextso high-severity findings can be restricted to security personnel - Cost allocation: per-team cost allocation with
dt.cost.centerthat flows into consumption reporting - Custom bucket routing: send critical findings to a long-retention bucket while everything else uses the default
VULNERABILITY_STATE_REPORT_EVENT, VULNERABILITY_ASSESSMENT_CHANGE_EVENT, VULNERABILITY_TRACKING_LINK_CHANGE_EVENT, and VULNERABILITY_STATUS_CHANGE_EVENT remain non-configurable, because a future release will deprecate them in favor of native concepts.
Action plan:
No action is required to keep data flowing. All events will flow into the new default_security bucket automatically.
Act before Dynatrace version 1.353 if either applies:
- You query security events by bucket name. Notebooks, dashboards, and workflows filtering on
default_securityeventsordefault_securityevents_builtinneed updating. - You rely on retention beyond 35 days. Either extend the retention of
default_security, or add an OpenPipeline routing rule sending the data you need to keep to a longer-retention bucket.
For more information, see the security events migration guide.
Cost Intelligence
Billing Usage Events versioning harmonization
Starting with Dynatrace version 1.350, to harmonize versioning across Billing Usage Events, Dynatrace updates every event.version to three-tier versioning, MAJOR.MINOR.PATCH (for example, 1.0.0).
If you filter on event.version in a custom DQL query, this is a breaking change.
Action plan:
Remove the version filter from your query instead of updating it to the new format. You don't need to filter on the version in DQL.
Platform | Dashboards
Stricter validation for dashboard query limits and analyze and alert options
Starting with Dynatrace version 1.350, Dynatrace applies stricter rules to dashboards and will remove these options if they don't pass validation:
- Query limits:
tiles.*.querySettings - Analyze and alert:
tiles.*.davis
What dashboards are affected?
This will mainly affect dashboards created or modified via the API or external AI tools. Dashboards created and maintained using Dashboards can't fail validation unless you modify them otherwise.
Dashboard tiles that contain invalid data in the querySettings or davis configuration in their JSON will see those settings removed. In most cases, the invalid configurations were not being applied in the UI, and the tile either showed an error, or was applying default values.
Under some circumstances, however, this might mean that some query limits (querySettings) and analyze and alert options (davis) are removed.
Action plan:
The old configuration can be recovered from the version history and re-applied following these steps:
- Open the dashboard and select Version history from the dashboard menu.
- Find a version from before this change and download it.
- Select Edit JSON from the dashboard menu.
- Inside the code editor, update the JSON with the contents of the downloaded dashboard. Errors in
querySettingsanddaviswill be shown, and you will need to resolve them to continue.
Fixes and maintenance
Resolved issues in this release (SaaS)
- Fixed an issue where maintenance window start and end events weren't ingested into Grail. (PS-52181)
- Changed snapshot compatibility checking to use sprint versions. The current version and the previous sprint version (n-1) are now supported. (PS-50530)
- Fixed a problem where redirecting to an extension from a pipeline or ingest source was not working. (PPX-15971)
- Fixed an issue that caused an error message to be displayed twice. (PPX-15919)
- Fixed an issue where some metrics were not ingested for an extended period after a license renewal. (PPX-15580)
- Fixed left and right axis assignment on time series tiles with two metrics. The assignment now follows the field order in the data-mapping panel: the first field uses the left axis, and a field with a different unit uses the right axis. Existing tiles may show the axes swapped; reorder the fields in the data-mapping panel to restore the layout you want. (PAPA-36830)
- Metric names starting with
dt.are reserved for Dynatrace-internal use. When the Advanced OTLP Metrics Dimensions setting is enabled, any such metrics ingested via/api/v2/otlp/v1/metricsare now dropped on ingest. (ICP-9836) - Fixed incorrect results when
:fold(<aggregation>)was followed by:rateand the aggregation was not among the metric's supported aggregations. The:rateoperator calculated over a single timeslot instead of the whole timespan. (GRAIL-56104) - Fixed an issue where saving central enrichment configuration on Azure-hosted environments failed because of an invalid storage metadata name. (DAQ-30928)
- Fixed recurring warnings about an unfinished central enrichment migration for cloud connections that are not monitored, for example because of invalid credentials. Connections without legacy enrichment rules now finish the migration. (DAQ-30786)
- GCP dimension names from central enrichment rules are no longer truncated to 32 characters. (DAQ-30455)
- Cloud connections are now migrated to the central enrichment configuration when the environment switches to the final migration stage. (DAQ-30205)
- Central enrichment rules that use GCP labels as a source are now applied to GCP metrics and logs. (DAQ-30071)
- Enrichment migration no longer fails for cloud connections whose existing settings do not pass current validation. (DAQ-30045)
- Cloud connections that still use legacy enrichment now keep their tags and security context until they're migrated to the central enrichment configuration. (DAQ-30012)
- Fixed a connection leak that caused requests to keep failing after an upstream service recovered from an outage. Affected services no longer need a manual restart to recover. (DAQ-29724)
- Deleting a central enrichment configuration that was already deleted now succeeds and no longer floods the logs. (DAQ-29698)
- Fixed extension asset information not being returned when some assets could not be retrieved at request time. (DAQ-29528)
- Fixed an issue where sending emails sometimes failed with a 503 error right after deployment. (CLIN-34845)
- Fixed negative billing amount values in the Adaptive Traffic Management and trace capture dashboard. (APPOBS-40804)
- Fixed search input overlapping the Tracing tab label in the snapshot detail pane at narrow widths. (APPOBS-39762)
- Fixed an issue where telemetry didn't run unless Git was installed. (APPDEV-20310)
- Fixed CSV export so that each row is formatted from its own entry instead of from the first entry only. (APPDEV-20217)
- Fixed time series area charts that stacked values instead of showing each one independently when data points had a center timestamp but no end value. (APPDEV-20154)
- Fixed chart tooltips so that long series names wrap correctly and no longer stretch the tooltip beyond its maximum width. (APPDEV-20098)
- Fixed out-of-memory errors on macOS and Linux when building apps with many settings widgets. (APPDEV-19971)