Rollout start: Jan 20, 2025
As announced earlier, the Dynatrace AWS log forwarder is deprecated.
Breaking change End of support for the Dynatrace AWS log forwarder was Dec 31, 2024.
If you are still using the deprecated AWS log forwarder, we recommend that you switch to the new Unavailable in Dynatrace Managed.
Breaking change
This release ends the transition period for custom attribute case-sensitivity changes.
Starting with this release (Dynatrace Managed version 1.306):
Custom attribute keys have to be case-sensitively unique, which means that custom attributes differing only in letter case are no longer treated as the same attributes. For example, it is now possible to define two different custom attributes named MyAttribute and myattribute.
Searches become case-sensitive (except for filter-only attributes). For example, if you define a custom attribute MyAttribute, then a search for MyAttribute="SEARCH" will return log events having this particular attribute value set to SEARCH but myattribute="SEARCH" will not.
Query values remain case-insensitive. For example, MyAttribute="SEARCH" is equivalent to MyAttribute="search".
Application Observability | Distributed Traces
Every attribute listed in the classic trace view, on the Summary tab, section OneAgent attributes, can be used for custom request names.
Platform | Problems
A new default limit of 1,000 unique complex event title/description filters counted over all Alerting Profiles has been introduced.
An event title/description filter is considered complex if it is either a contains operator with case sensitivity turned off, or a contains regex operator.
An Alerting Profile with only a single unique complex event title/description filter does not count toward the maximum limit.
Infrastructure Observability | Kubernetes
Kubernetes monitoring restart has been minimized on Kubernetes settings update without actual content change.
Infrastructure Observability | Kubernetes
The toggle Monitor persistent volume claims has been removed, as the persistent volume claim metrics are now ingested as built-in metrics by default. For details, see Introducing built-in Persistent Volume Claim Monitoring for Kubernetes.
Infrastructure Observability | Log Analytics
Added two new attributes, User name and Keywords, both from Windows event logs, to Log Viewer and as matchers in an ingest configuration.
Infrastructure Observability | Hosts
The descriptions of Infrastructure metrics on the Metrics browser page and the Metric selector in the latest Dynatrace have been unified.
Metrics Ingestion Protocol
In OTLP (OpenTelemetry Protocol) metrics ingest, the default allow list for resource and scope attributes to be taken over as metrics dimensions was extended.
Several attributes in the k8s.* and dt.* namespace were added as well as service.instance.id.
If the new attributes are not desired, the individual toggles can be turned off under Settings > Metrics > OpenTelemetry metrics > Allow list: resource and scope attributes (or the entry can be removed altogether).
The Anonymization API - PUT anonymization job supports anonymization of user sessions based on an internal application ID via the parameter requestId (or clusterRequestIds for Premium High-Availability clusters).
To learn about changes to the Dynatrace API in this release, see: