Dynatrace SaaS release notes version 1.269
Rollout start: Jun 20, 2023
Want to ask questions or give feedback? Head over to What's New in Dynatrace in the Dynatrace Community.
New features and enhancements
Entry point information for code-level vulnerabilities
Application Security | Vulnerabilities
To help you get to the source of a code-level vulnerability and determine exactly what is needed to resolve it, entry point information is now displayed on the details page of the vulnerability. For details, see Entry points.
Additional events in vulnerability evolution
Application Security | Vulnerabilities
Vulnerability evolution now shows these events:
- Davis Security Score changed
- CVSS Score changed
- Risk assessment changed
- Number of reachable data assets
- Public internet exposure
- Public exploit available
- Vulnerable function usage
- The number of affected process groups changed
- The number of affected nodes changed (only for Kubernetes vulnerabilities)
- Attacks detected (only code-level vulnerabilities)
Double ingest period when upgrading to Log Management and Analytics
Infrastructure Monitoring | Logs
Activating logs on Grail now includes the option to start a double ingest period (7 days), during which time your data continues to be stored as usual and in Grail. After the waiting period, when you automatically switch to Log Management and Analytics powered by Grail, you start with that existing 7 days of data.
Configure timestamp format without a year
Infrastructure Monitoring | Logs
In log monitoring, when creating a rule with a pattern without a year specifier, the current year will be used to evaluate the timestamp. This option requires OneAgent version 1.267 or higher.
Init container support
Infrastructure Monitoring | Kubernetes
We added parsing of the init containers. The following metrics now include occurrences of initContainer
; therefore, you might experience an increase in numbers there.
builtin:kubernetes.container.oom_kills
builtin:kubernetes.container.restarts
Additionally, names of init containers now appear in the values of the k8s.container.name dimension and in log lines.
New design of service and database overview pages
Apps & Microservices | Distributed traces
The unified analysis page framework is now available for the service and database pages. The new design supports faster troubleshooting with fewer steps:
- Interactive microcharts that add focus on suspicious patterns
- (Key) Requests directly on the overview page
- Davis exploratory analysis
- Traces, logs, service metrics, and SLOs in context
- Improved topology visualization
To switch to the new design, turn on Try it out at the top of the overview page. To revert to the classic design, select More (…) > Return to classic page on the overview page.
Share your feedback in the Feedback channel for the new opt-in OneAgent and DB services’ pages - v1.269 (SaaS), v1.270 (Managed) in the Dynatrace Community!
OTLP logs ingest endpoint
OpenTelemetry
You can now ingest OpenTelemetry logs using the OpenTelemetry Protocol (OTLP) as a binary Protobuf over HTTP.
For more information, see Ingest OpenTelemetry logs.
Dynatrace REST API audit logs for platform services
Cross Solutions | Audit logs
Audit logs are collected on the API Gateway for all platform services that are exposed to AppEngine and App Development. Every service exposed there has the additional value of automatic REST API audit logging built in.
-
All REST API audit logs are stored inside of the Audit log bucket in Grail as system events for one year.
-
You can use DQL queries and the Dashboards or Notebooks apps to analyze your calls or base a workflow on your REST API audit logs.
-
Every audit log contains the API path, error codes, and authentication context, and other helpful metadata of the request is stored so you can analyze activity in your environment.
Dynatrace API
To learn about changes to the Dynatrace API in this release, see Dynatrace API changelog version 1.269.
Resolved issues
General Availability (Build 1.269.92)
The 1.269 GA release contains 2 resolved issues.
es client
- Improved calculation of the average consumed disk of Elasticsearch to prevent false positive warnings about disk space consumption. (CLUSTER-7054)
storage
- Disabled new method for reading of permissions that was optimized for large numbers of Monitored Entities because it caused performance problems for some deployments. (CLUSTER-7095)
Update 99 (Build 1.269.99)
This is a cumulative update that contains all previously released updates for the 1.269 release.
Update 103 (Build 1.269.103)
This is a cumulative update that contains all previously released updates for the 1.269 release.
Update 117 (Build 1.269.117)
This is a cumulative update that contains all previously released updates for the 1.269 release.
Update 121 (Build 1.269.121)
This cumulative update contains 3 resolved issues and all previously released updates for the 1.269 release.
Cluster
- Fixed a permission problem that prevented users from accessing multidimensional analysis. (TI-7266)
- Opening the multidimensional analysis from "Data explorer" when viewing a calculated service metric no longer requires calculated service metric configuration permissions. (TI-7076)
metric query
- Fixed issue with missing dimensions for the metrics "Host availability %" and "Process availability %". (CLUSTER-7173)
Update 130 (Build 1.269.130)
This is a cumulative update that contains all previously released updates for the 1.269 release.
Update 142 (Build 1.269.142)
This cumulative update contains 20 resolved issues and all previously released updates for the 1.269 release.
ActiveGate
- ActiveGate monitoring is no longer affected when ActiveGate synchronizes the clock backward. (K8S-6034)
Application Security
- Fixed an issue that caused the "Change status" button and the bulk muting confirmation button on the remediation tracking page to be disabled for users with partial management zone permissions. Buttons are now displayed as enabled, and the permission check is delegated to the API in case of partial management zone permissions. (RSA-10126)
- Code-level vulnerabilities now also contain information about their entry points. An entry point is the source of a vulnerability and displays information like the URL or HTTP parameter that was used to hit the vulnerability. (RSA-8072)
Infrastructure Monitoring
- Corrected the aggregation type for the `builtin:host.dns.queryCount` and `builtin:host.dns.errorCount` metrics from AVG to SUM. (HOST-2992)
Synthetic monitoring
- Fixed an error related to the list of events included in the response body when retrieving the details of a Synthetic browser monitor using the API. (SYNTH-5176)
- Improved data source handling in execution details to prevent exceptions that occurred in certain situations. (SYNTH-4751)
User Interface
- Improved generated access token presentation to only partially display the secret in the web UI by default; just the first public part is displayed in a single line input, not a multi-line text area. (UIP-3819)
es client
- Improved calculation of the average consumed disk of Elasticsearch to prevent false positive warnings about disk space consumption. (CLUSTER-7054)
metric query
- Fixed issue with missing dimensions for the metrics "Host availability %" and "Process availability %". (CLUSTER-7173)
- Fixed negated metrics leading to errors on aggregation in metric selectors. (CLUSTER-6773)
Session Replay
- Fixed an issue in which, when two or more Session Replay tabs were open, there was a mismatch in the HTML content. Each session is now shown properly. (SR-2192)
Cluster
- Fixed a permission problem that prevented users from accessing multidimensional analysis. (TI-7266)
- Fixed an issue where in some cases, Application Security monitoring rules evaluation only considered the currently added/edited rule instead of all available rules, leading to a wrong monitoring state of entities and a wrong usage consumption. (RSA-10512)
- Fixed an issue where a dashboard tile can't display any data in rare cases. (EXA-6633)
- The correct threshold is now reported when reporting problems resulting from metric events using the auto-adaptive baseline monitoring strategy. (The baseline/threshold given in the problem description was outdated. The alerts themselves were not affected and were correct.). (DAVIS-4848)
- Fixed an issue that, in rare situations, caused a manually closed problem to reopen after a maintenance window had ended. (DAVIS-4765)
- Fixed an issue where JavaScript agent build units could not be downloaded for newly created tenants on new clusters. (RUM-11774)
- The filter field expression in VMware settings now accepts null values. (HOST-3011)
- Opening the multidimensional analysis from "Data explorer" when viewing a calculated service metric no longer requires calculated service metric configuration permissions. (TI-7076)
storage
- Disabled new method for reading of permissions that was optimized for large numbers of Monitored Entities because it caused performance problems for some deployments. (CLUSTER-7095)