Dynatrace Inc.

08/12/2024 | Press release | Archived content

Dynatrace SaaS release notes version 1.298

Rollout start: Aug 12, 2024

New features and enhancements

CLV and attack monitoring rules now based on resource attributes

Application Security | Code-level VulnerabilitiesApplication Security | Attacks

The monitoring rules criteria for code-level vulnerabilities and attacks now allow matching based on resource attributes instead of the process group ID.

The process group ID field is removed and automatically migrated to an equivalent rule based on resource attributes. Removing the process group is also done in Settings - Objects API for the schemas:

To continue using the process group in these APIs, you need to explicitly state the , and Dynatrace will automatically convert these rules to use resource attributes instead.

When you create resource-attribute-based monitoring rules in Settings:

  • You get suggestions for resource attribute keys and values based on your environment.
  • You can verify that the selected resource attribute conditions have the desired effect by selecting Preview matching process group instances, which lists process group instances that would currently match the criteria.

For details, see

Unified ingest supports vulnerability findings for AWS ECR enhanced scan

Platform | OpenPipelineApplication Security | Vulnerabilities

You can now seamlessly ingest AWS Elastic Container Registry (ECR) vulnerability findings provided by Amazon Inspector with enhanced scanning and operationalize your data on the Dynatrace platform.

Our sample dashboard , workflow for Jira tickets , and workflow for Slack notifications can help you visualize data and automate notifications.

For details and instructions, see Ingest AWS ECR vulnerability findings.

Dashboard version management

Dashboard versions are now saved automatically.

  • You can access the 50 most recent versions of your dashboard.
  • Each dashboard version is available for up to 30 days.

For details, see Manage document versions.

Webhook integration for problem notifications

Platform | Problems

The webhook integration for problem notifications now supports the oAuth2 basic header authentication flow.

Problem REST API and notification enhancements

Platform | Davis

Three new fields are returned when querying problems via the REST API:

The new fields include the combined information of all events on the problem (if available).

  • This information is also available via the integration placeholder.
  • Problem notifications have been adapted to contain additional attribute information of problem events.

Custom injection rule configuration moved

Digital Experience | RUM Web

Custom injection rules have been moved.

  • Before: Application settings > Injection > Injection
  • After: Application settings > Injection > Custom injection rules

ActiveGate host-based installer on ARM architecture

Infrastructure Observability | Hosts

The ActiveGate host-based installer is now also available on ARM architecture. It supports only routing and monitoring capabilities.

PGI relation added to OS Service page

Infrastructure Observability | HostsPrevious Dynatrace

The process relation has been added to the Properties and tags section of the OS Service page.

Infrastructure & Operations: GeoLoc Site priority lower than regular data centers

Infrastructure Observability | HostsInfrastructure & Operations

The GeoLoc site is used as a data center only for hosts without any other data center detected.

Interaction to Next Paint metric

Digital Experience | RUM WebOneAgent version 1.297+

The Core Web Vital metric Interaction to Next Paint (INP) () has been added to allow for the analysis of the general responsiveness of a web page.

Dynatrace API

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

Dynatrace SaaS resolved issues

General Availability (Build 1.298.27)

The 1.298 GA release contains 9 resolved issues.

Dynatrace Cluster

  • Custom metric-based disk events can now merge with built-in disk events into the same problem. (DI-15443)
  • MonitoringState REST API now accepts 'from' and 'to' time selection. Only statuses for active entities in the selected timeframe are returned. (HOST-6406)
  • Resolved issue in which Azure Standard Load Balancer service did not monitor all the load balancers, omitting some that were previously successfully monitored by the older service, Azure Load Balancer (built-in). Removed filtering that too aggressively excluded LBs from being monitored despite them having traffic and metrics. (PCLOUDS-4568)
  • Fixed an issue that caused a server error when the synthetic monitor had no assigned location. (SYNTH-12150)
  • Muting requests per API for a huge number of entities simultaneously (for example, by script) should perform better now and not lead to timeouts. (PS-24848)
  • Fixed an issue in the mobile waterfall where the "View Trace" button was missing for AWS Lambda backends. (RUM-20732)
  • If service detection rule evaluation ends with an empty service name, the matched rule is skipped and the default service detection rule is applied. A new `CallFlaw EMPTY_SERVICE_NAME_FROM_SD_RULES` is introduced to indicate such cases. (TI-13280)

OneAgent

  • The file system type field used for disk exclusion in Disk Options now supports case-insensitivity. (HOST-6322)

User interface

  • Logs with attributes whose values are object arrays will now display said objects as a string. (LOG-7547)

Update 28 (Build 1.298.28)

This cumulative update contains 2 resolved issues and all previously released updates for the 1.298 release.

Dynatrace Cluster

  • Fixed an issue where offline PGIs were still considered for monitoring and usage. (RSA-17167)
  • Fixed an issue where PGIs excluded from monitoring were generating usage. (RSA-17259)