Your opinion matters. Complete the two-minute feedback survey and shape how we present feature updates, breaking changes, and upcoming changes in the future.
This page showcases new features, changes, and bug fixes in Dynatrace SaaS version 1.313. It contains:
Kubernetes | Log Analytics
The Dynatrace Log Module for Kubernetes provides you with automated, centralized log collection—all without needing OneAgent on every node.
With our enhanced Log Module for Kubernetes, you get:
No more manual log shipping
Centrally manage logs across your clusters, eliminating the hassle of configuring individual log collectors.
Insights into short-lived containers
Easily analyze logs from init containers, jobs, and ephemeral workloads that were previously difficult to capture.
Fine-grained log access controls
Define who can access logs at the namespace or cluster level for better security and compliance.
Flexible observability
Start with Kubernetes platform monitoring, then scale up to full-stack observability—including traces, security analytics, and real-user monitoring.
All | Monitoring Consumption
We have improved the documentation for DPS Host monitoring in SaaS (including Full-Stack Monitoring and Infrastructure Monitoring) to make it more clear which metrics and spans are covered by the included volume in the Full-Stack Monitoring and Infrastructure Monitoring capabilities.
When you have the Metrics powered by Grail capability on your rate card, metrics that are scraped and sent via the Dynatrace OpenTelemetry Collector in Kubernetes are now covered by the metric data points volume in Full-Stack or Infrastructure monitoring if the underlying host is monitored via OneAgent by either leveraging Classic Full-Stack or Cloud Native Full-Stack deployment.
For details, see Host monitoring: Metrics.
As in all other scenarios, metric data points that exceed your included volume of metric data points are charged as Metrics powered by Grail - this explicitly includes Prometheus metrics sent via ActiveGate, which will be enforced now.
Trace data sent via the OneAgent Trace API or, more generally, OpenTelemetry traces that originate at a Full-Stack Monitoring host or application and are sent via the OTLP API are now also counted into the included trace data volume. Any OpenTelemetry trace data that is sent this way that exceeds your included trace-data volume in a given 15-minute interval is charged as Traces - Ingest & Process.
For details, see Host monitoring with Dynatrace.
Platform | DQL
The query execution events available in dt.system.query_executions
provide visibility into the query load in Grail, with precise context of query source. You can now retrieve the client context and failure reason in case of failed queries.
Sample query:
fetch dt.system.query_executions| filter status == "FAILED"| filter client.application_context == "dynatrace.dashboards"| filter failure_reason == "INSUFFICIENT_PERMISSIONS"
Context-specific information allows you to perform detailed analysis of failed queries. As usual, the full power of DQL is available to make use of this additional source of data.
For more information, see Query Execution Events in the Semantic Dictionary.
Software Delivery | Site Reliability Guardian
The redesigned app header in the Site Reliability Guardian is streamlined for a more intuitive interface, providing simplified navigation and easier access to help and documentation.
For app details, see Site Reliability Guardian.
Platform
dt.security_context
You can now use dt.security_context
in metric extraction for logs, spans, and events. Note: Metric extraction from spans requires the DPS rate card Metrics Ingest and Process.
Application Security | Vulnerabilities
You can now set up monitoring rules based on resource attributes (for processes) and Kubernetes labels (for Kubernetes nodes and hosts) in Settings > Application Security > New monitoring rules: Third-party.
For detailed information, examples, and use cases, see Monitoring rules - Third-party Vulnerability Analytics and Use cases for monitoring rules.
Workflows | Connectors
You can now start setting up your Workflows Connectors directly in Dynatrace Hub.
Platform | Dashboards
We now offer variable replacement strategies when referencing variables in DQL tiles.
While introducing new strategies, we adapted the default strategy, which automatically wraps variable values with double quotation marks on replacement in the tile. Previously, quotation marks within such variable values were automatically removed to avoid breaking queries. We have improved this by escaping quotation marks within variable values instead.
This change enhances the transparency of the actual values to the user and the security. If you now encounter unwanted quotation marks in your variable values, remove them at the source (on ingest) or use DQL functions (on read).
Default replacement: replaces the variable with its value using double quotes. It is useful for Strings such as entity names or categories.
Example: $variable
Escape double-quotes in variable values.
No-quote replacement: Replace the variable with its value without adding quotes.
Example: $variable:noquote
Values can only include alphanumeric characters, underscore (_
), dash (-
), and dot (.
). Query will show an error on query execution for other characters.
Triple-quote replacement: Replaces the variable with its value using triple quotes, allowing raw content without escaping.
Example: $variable:triplequote
Show an error if """
is part of the value on query execution.
Backtick replacement: Replaces the variable with its value using backticks, useful for field names in DQL.
Example: $variable:backtick
Escape backticks in variable values.
For details, see Variable replacement.
Dynatrace Hub
Effective July 1st, the URL for the Dynatrace Hub CDN will change from https://dt-cdn.net/hub
to https://cdn.hub.central.dynatrace.com
. If you directly access Hub CDN URLs, for example to download extensions within your network, you must update your network configuration accordingly. To avoid any disruptions, please ensure that the new URL, https://cdn.hub.central.dynatrace.com
, is added to your allowlists alongside https://dt-cdn.net
at your earliest convenience.
cloud:aws:rds
and cloud:aws:rdsaurora
, along with corresponding OpenPipeline Technology bundles, now link logs to both RELATIONAL_DATABASE_SERVICE
and CUSTOM_DEVICE
entities to support both legacy and generic AWS integrations. (APPOBS-4827)To learn about changes to the Dynatrace API in this release, see Dynatrace API changelog version 1.313.