What's new in Dynatrace SaaS version 1.310

  • Release notes
  • 10min
  • Mar 11, 2025

This page showcases new features, changes, and bug fixes in Dynatrace SaaS version 1.310.

To learn about new Dynatrace Apps and feature updates with this release, select an item from the table below.

Category
Updates in this release
10

Across platform

Feature update Dot Platform | Distributed Tracing

Distributed Tracing powered by Grail

Distributed Tracing powered by Grail is now in General Availability. Traces powered by Grail allow you to access your trace data with the fetch span DQL command across the platform, providing you with powerful capabilities to:

  • Solve advanced trace analytics use cases with DQL
  • Extend your trace retention up to 10 years
  • Extend the trace ingest rates

For more information, see:

As part of this general availability, the Traces powered by Grail product category has been introduced and is available to DPS customers. You can find more details in the full rate card.

Feature update Dot Application Observability - Services

Calculated service metrics in Grail

Calculated service metrics are now available in Grail.

  • Enhanced precision: Grail stores the metrics' full dimension cardinality—not just the Top X values—providing more accurate insights.
  • Seamless data exploration: Use the power of DQL and the new Dashboard Dashboards to explore, filter, and analyze your metrics with ease.
  • Improved flexibility: Placeholders used in the metric's dimension values are now separated into distinct metric dimensions, making querying and dashboarding simpler.
  • Coming soon Services App Integration: Metrics upgraded to Grail will automatically appear in the Services Services app’s Metrics tab for effortless access alongside other service data.

What you need to know

  • Automatic upgrade: Most calculated service metrics will be automatically upgraded to Grail.
  • For metrics that can’t be automatically upgraded, use OpenPipeline app OpenPipeline or create a DQL report in Notebooks Notebooks to access similar insights. For details, see Calculated service metrics upgrade guide.
  • Future direction: All new calculated service metrics should be created via metric extraction from span data in OpenPipeline app OpenPipeline. This approach provides greater flexibility and control. Note that the current calculated service metrics functionality will be deprecated in the future (there's no deprecation date yet; details will follow).

Coming soon

  • Improved Listing: The Settings Settings Classic app will soon include better filtering/tracking for migrated calculated service metrics.
  • Adjustments for Services App: As noted in the upgrade guide, some calculated service metrics may need adjustments to display correctly. These adjustments are still not applied to the Services Services app. For now, we recommend opening calculated service metrics in Notebooks Notebooks via the Open with button from the Settings Settings Classic app, as the generated DQL automatically applies the necessary adjustments and provides a DQL query that can be used as a foundation for other queries or dashboards.

Feature update Dot Grail | DQL

New XML matcher parameter

You can now use the ignoreNamespace parameter with the following XML matchers with DPL:

Feature update Dot Infrastructure Observability

Resilient updates for Environment ActiveGates

We're excited to announce enhancements to the ActiveGate auto-update mechanism. The new update process ensures that updates within network zones, ActiveGate groups, and Synthetic private locations are performed in a rolling fashion. These improvements brings several benefits:

  • Minimized downtime: By updating ActiveGates sequentially, we reduce the risk of service interruptions.
  • Enhanced stability: Rolling updates ensure that only a subset of ActiveGates is updated at any given time, maintaining overall system stability.
  • Improved reliability: This method allows for better monitoring and quick interruption if any issues arise during the update process.

These changes will significantly enhance the performance and reliability of ActiveGate deployments.

Feature update Dot Application Security | Code-level vulnerabilities & Attacks

Detection of SSRF vulnerabilities and attacks on Java

OneAgent version 1.309+

Detection of server-side request forgery (SSRF) is now supported for code-level vulnerabilities and attacks in Java technology.

To enable SSRF monitoring, follow the instructions below.

  1. Enable OneAgent monitoring: In Settings > Preferences > OneAgent features, turn on Java SSRF code-level vulnerability and attack evaluation and make sure that Java code-level vulnerability evaluation is turned on.
  2. Verify Runtime Vulnerability Analytics settings: In Settings > Application Security > Vulnerability Analytics > General settings, make sure that Enable Code-level Vulnerability Analytics is turned on and Global Java code-level vulnerability detection control is set to Monitor.

Feature update Dot Runtime Application Protection | Attacks

Enhanced allowlisting capabilities for attacks

OneAgent version 1.309+

When creating a rule to allowlist an attack (Settings > Application Security > Application Protection > Allowlist), you can now

  • Filter specific attacks with more precise control
  • Define conditions that must be met to allowlist an attack
  • Specify where the rule is applied

Feature update Dot Runtime Vulnerability Analytics | Vulnerabilities

Support for Python technology

OneAgent version 1.309+

Dynatrace extends the list of supported technologies for Runtime Vulnerability Analytics to include Python.

To detect Python vulnerabilities

  1. Enable Dynatrace monitoring: In Settings > Monitoring > Monitoring technologies, find Python and enable Monitor Python.
  2. Enable OneAgent monitoring: In Settings > Preferences > OneAgent features, find and enable Python software component reporting, then restart your processes.
  3. Enable Runtime Vulnerability Analytics monitoring: In Settings > Application Security > Vulnerability Analytics > General settings, enable Python.

Feature update Dot Application Security | Third-party vulnerabilities

Python support for the origin of vulnerable components

OneAgent version 1.309+

Information regarding the origin of the vulnerable component is now available for Python software components on the remediation tracking pages for process groups and processes affected by a vulnerability.

Feature update Dot Platform | Platform Services

Additional audit events for Dynatrace REST API usage

Dynatrace now provides access to additional audit events in dt.system.events for keeping track of which Dynatrace REST APIs are used.

API calls now get audited in dt.system.events via the following:

  • event.kind == "AUDIT_EVENT"
  • event.provider == CLASSIC_API

The fields resource and event.type allow you to filter for specific APIs.

Sample query:

fetch dt.system.events
| filter event.kind == "AUDIT_EVENT"
| filter event.provider == "CLASSIC_API"
| filter event.type == "POST"
| filter contains(resource, "entity")

Context-specific information allows you to deeply analyze the data. As usual, the full power of DQL is available to make use of this additional source of data.

Upcoming change Dot Platform

IP address changes of OneAgents and ActiveGates connecting to Dynatrace SaaS

In March 2025, Dynatrace will change the underlying IP addresses that ActiveGates and OneAgents use when connecting to Dynatrace SaaS on AWS. This will result in a change of frontend IP addresses.

  • This change will be completely transparent and won't require immediate action.
  • Later this year, however, action may be required, depending on your deployment.

For more information, see IP address changes of OneAgents and ActiveGates connecting to Dynatrace SaaS.

Platform bug fixes, patches, and maintenance

  • Built-in log processing rule cloud:aws:lambda links logs to both AWS_LAMBDA_FUNCTION and CUSTOM_DEVICE entities to support both AWS integrations (AWS Lambda and AWS Lambda built-in). (APPOBS-1018)

  • Fixed an issue that broke metric queries that use more than one ne filter inside an or filter. (MGD-3063)

  • Fixed duplicated types for the limit override for DevOps Alerting setting on the web UI. (DI-19122)

  • Service metrics in Grail derived from aggregated spans (for example, database calls) are now multiplied correctly based on the aggregation count. (APPOBS-5177)

  • Fixed the name formatting for the root cause entity in the Problems card. (DI-19131)

  • ActiveGate extension modules: in the case of a corrupted module version, the version is normalized to allow for successful module update. (MGD-2961)

  • Mobile Session Replay: Fixed an issue in which some images in some sessions were not being loaded because the timeframe used to request them was wrong. (DEM-6048)

  • Dashboards Classic: Resolved an Error 431 that resulted when selecting "View Synthetic event" from a dashboard tile. (DEM-5401)

  • Dashboards Classic: Timeseries with one-hour resolutions are no longer shifted to display grouped data points at the beginning of the resolution timeframe. (PAPA-23431)

Dynatrace API

To learn about changes to the Dynatrace API in this release, see Dynatrace API changelog version 1.310.