Dynatrace SaaS release notes version 1.262
Rollout start: Mar 14, 2023
New features and enhancements
Management zone selector returns exact management zone matches
Application Security | Vulnerabilities
On the Third-party vulnerabilities and Code-level vulnerabilities list pages, when you filter by a management zone, the vulnerabilities without management zones are now excluded from results.
SLOs can now be defined for metrics / entities not available yet
Cloud Automation | SLOs
We now better support config-as-code and application onboarding use cases.
SLOs now can be defined by referring to metrics, especially custom metrics, and filtered for entities, even before those are monitored by Dynatrace.
This allows decoupling of the SLO specification and the point in time when the monitored software gets deployed and monitored.
SLOs in the entity overview pages
Cloud Automation | SLOs
SLOs and burn rates can be created, assigned, and displayed in the toolbar of entity overview pages created with the unified analysis framework, such as host, service, or Kubernetes workloads overview pages.
Custom alerting profile filters available for all event types
Cross Solutions | Davis AI
Event filters for problem alerting profiles under the Custom source are now available for all event types, including built-in events, for example, events raised through OneAgent monitoring.
Existing problem alerting profiles may now match more problems.
We recommend reviewing your existing event filters.
New DQL command
Cross Solutions | DQL
Now you can include the following command in your DQL queries:
- lookup
Thelookup
command adds (joins) fields from a subquery (thelookup table
) to the source table by finding a match between a field in the source table (sourceField
) and the lookup table (lookupField
).
Changes to OneAgent updates
Cross Solutions | OneAgent update
Settings 2.0 schema
You can manage OneAgent updates using Settings 2.0 OneAgent updates schema. Access permissions to the OneAgent updates page can also be granted with this schema (builtin:deployment.oneagent.updates
).
OneAgent target version
You can now define a relative target version (latest stable version, previously stable version, or older stable version) or precisely specify the target version and revision for OneAgents. The version and update mode can be set for the whole environment, a host group, or an individual host.
Even if you select a version older than the version currently deployed, you won't be able to downgrade OneAgent. You can only install a newer version over an existing OneAgent version.
Service label filters
Infrastructure Monitoring | Kubernetes
Support for the multi-filtering was added for the Kubernetes lists pages. The following filters are multi-filtering capable:
- Namespace, workload and service labels
- Service type
- Workload type
- Pod phase
Now, filtering for multiple pod phases is possible. If applied, the filters work as a logical OR.
Multi-filter support
Infrastructure Monitoring | Kubernetes
Multi-filtering is enabled on the Kubernetes list page for the following filters:
- Namespace labels
- Service type
- Workload type
- Workload labels
- Pod phase
Now the filtering is possible for multiple pod phases.
Alerts for persistent volume claims
Infrastructure Monitoring | Kubernetes
Out-of-the-box alerts for persistent volume claims have been added to the Kubernetes cluster and namespace settings.
Cloud platform property
Infrastructure Monitoring | Hosts
The Cloud platform type property is added to the host properties page for Kubernetes, OpenShift, and Cloud Foundry hosts.
New property for the OpenStack hosts
Infrastructure Monitoring | Hosts
The Region relation property is now available for the OpenStack hosts on the host properties page.
New charts in the host performance chart group
Infrastructure Monitoring | Hosts
On the host page, the following charts are now available in the host performance chart group:
- For the VMware hosts:
- Physical CPU
- CPU ready time
- Memory compression
- Memory swapping
- For the OpenStack hosts:
- CPU OpenStack
- Disk space allocation
- For the AWS hosts:
- CPU AWS
- For the Azure hosts:
- CPU Azure
Maintenance windows markers in the host performance charts
Infrastructure Monitoring | Hosts
Introduced a new grey-color marker on the host performance charts which indicates when the maintenance window was present for this host.
Availability uptime respecting maintenance windows
Infrastructure Monitoring | Hosts
We've changed the way availability uptime is calculated on a page for a single host. Previously we calculated the uptime based on all available data regardless of the maintenance. Now, the data overlaying maintenance windows isn't taken into consideration.
Container injection problem in host and process group overview pages
Infrastructure Monitoring | Hosts
Host and process group overview pages now inform about the OneAgent container injection problem. Affected hosts and process groups now display a warning icon with information on the need to restart a container for the process to be monitored.
Username-password credential synchronization with CyberArk Vault
Digital Experience | Synthetic Monitoring
Infrastructure Monitoring | Extensions 2.0
You can now synchronize username-password credential pairs with CyberArk Vault. Dynatrace already offers username-password and token credential synchronization with Azure Key Vault and HashiCorp Vault.
Multiple on-demand synthetic monitor executions from the same location
Digital Experience | Synthetic Monitoring
When executing monitors on demand via API, you can now specify an execution count for repeated executions per location. The maximum execution count per location is 10.
By default, repeated executions are sequential, that is, triggered one after the other. However, you can also specify parallel executions, that is, repeated executions are triggered in parallel.
Override script parameters for on-demand synthetic monitor executions
Digital Experience | Synthetic Monitoring
Specifically for on-demand executions via API, you can override certain script parameters for HTTP as well as browser monitors. For example, you can override the request body, pre- or post-execution scripts, and request timeout, among other parameters for HTTP monitors. For browser monitors, you can override several parameters in the Navigate, Click, JavaScript, Keystroke, Tap, Select option, and Cookie events. Note that you cannot change the request method (or event type) or the number and order of requests/events.
Dynatrace API
To learn about changes to the Dynatrace API in this release, see Dynatrace API changelog version 1.262.
Resolved issues
General Availability (Build 1.262.115)
The 1.262 GA release contains 10 resolved issues.
Cluster
- User action and session properties added via the JavaScript API and declared public in the API call now overrule the doNotTrack mode. (RUM-9168)
- Increased a timeout for refreshing TenantStatistics to prevent Elasticsearch queries for larger environments from running into timeouts. (CLUSTER-5136)
- Fixed a problem where the RUM enablement setting on process group level was ignored, leading to unintentional enabling or disabling of RUM for certain process groups. (RUM-9579)
- UX score percentages are now consistent between buttons and charts. (RUM-9294)
- Service detection rules support the override of URL context roots with a constant value for service detection. This enables having all web-based services merged to a single service if they differ only by the URL context root. (TI-5536)
- We fixed an issue for Managed Multi-DataCenter failover handling where the event/problem handling could get stuck. (DAVIS-3625)
- Problems v2 and Events v2 APIs now use 413 instead of 403 as the HTTP error code if too much data is queried. (DAVIS-3534)
- Improved memory impact of user permission check for on-demand analysis. (CLUSTER-5013)
Application Security
- On the "Third-party vulnerabilities" page, added maximum length validation for the "Snyk/CVE ID" and "Tag" filters to prevent a Bad Request error page when input is longer than 48 characters. (RSA-8496)
Autonomous Cloud
- The "Monitor Kubernetes / OpenShift" deployment page now references the newly released Dynatrace Operator v0.10.3. (K8S-5162)
Update 121 (Build 1.262.121)
This is a cumulative update that contains all previously released updates for the 1.262 release.
Update 126 (Build 1.262.126)
This is a cumulative update that contains all previously released updates for the 1.262 release.