Want to ask questions or give feedback? Head over to What's New in Dynatrace in the Dynatrace Community.
Announcements
Synthetic Monitoring location changes
Digital Experience | Synthetic Monitoring
The Alibaba Sydney and Mumbai public Synthetic Monitoring locations will be discontinued by the end of March 2024.
In anticipation of this change, if you use the Alibaba Sydney or Mumbai locations, we recommend reassigning your monitors to alternative locations to ensure that your tests remain functional. If you prefer not to do this yourself, starting from March 2024, we will automatically transfer your monitors to alternative locations.
We have migrated all tenants to the latest Log Monitoring configuration page as an enhancement. The change affects environments currently using Logs Classic or powered by Grail that rely on the older configuration page.
Affected configuration pages:
Log sources and storage
This section is migrated to Log ingest rules:
timeseries
We added the shift parameter to the timeseries command.
New DQL functions
Platform | DQL
Now you can include the following functions in your DQL queries:
countDistinctApprox
Calculates the cardinality of unique values of a field for a list of records based on a stochastic estimation.
countDistinctExact
Calculates the cardinality of unique values of a field for a list of records.
Runtime metrics in Grail
Application Observability | Distributed traces
OneAgent-based runtime metrics are available in Grail and can be accessed and queried with Dynatrace Query Language. OneAgent version 1.283+ is required.
New feature flag for enabling @files support
Platform | OneAgent
The configuration option to expand Java VM options with parameters from @files is now enabled for improved process instrumentation and grouping.
Upgrade classic dashboards to Dashboards app
Latest DynatracePlatform | Dashboards
If you have classic dashboards with Data Explorer–based tiles, you can recreate them in the Dashboards app with one click.
Vulnerability: Improved input validation for Kubernetes settings. (K8S-6899)
Vulnerability: Improved input validation for Cloud Foundry settings. (K8S-6898)
The `getCredentialsDetails` resource from the Classic Dynatrace Environment API v2 SDK for Dynatrace apps now returns code 403 instead of 401 when the current user is authenticated but does not have access to the requested credentials. (SYNTH-9933)
Resolved an issue that prevented access to a few global settings pages for users with conditional IAM policies assigned. (PS-13100)
Services based on OpenIngest data can be inspected on Kubernetes workloads. (K8S-8814)
Fixed an infrequent case on single-server clusters where the event timeout information was not stored properly, causing new events to use the default timeout of 15 minutes and, for some events, possibly leading to events closing and reopening more often than expected. (DAVIS-7801)
Improved performance of OneAgent registration to avoid false positive alerts about monitored hosts being unavailable. (PS-12755)
Users can no longer revert extracted services if they don't have tenant-wide settings write permissions. (TI-11033)
Platform
Timestamp fields in workflow event triggers are now serialized in ISO format (were epoch nanoseconds before). This means the format of timestamps in the event trigger is aligned with timestamps as returned by Grail DQL queries. (PPX-898)
Synthetic Monitoring
Credentials shared with a list of users can now be filtered by the Shared access type. (SYNTH-9958)
Resolved an issue in which Synthetic monitors with shared credentials were editable by users who did not have access to those credentials. (SYNTH-9945)