Rollout start: Mar 14, 2023
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.
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.
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.
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.
Cross Solutions | DQL
Now you can include the following command in your DQL queries:
lookup command adds (joins) fields from a subquery (the lookup table) to the source table by finding a match between a field in the source table (sourceField) and the lookup table (lookupField).Cross Solutions | OneAgent update
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).
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.
Infrastructure Monitoring | Kubernetes
Support for the multi-filtering was added for the Kubernetes lists pages. The following filters are multi-filtering capable:
Now, filtering for multiple pod phases is possible. If applied, the filters work as a logical OR.
Infrastructure Monitoring | Kubernetes
Multi-filtering is enabled on the Kubernetes list page for the following filters:
Now the filtering is possible for multiple pod phases.
Infrastructure Monitoring | Kubernetes
Out-of-the-box alerts for persistent volume claims have been added to the Kubernetes cluster and namespace settings.
Infrastructure Monitoring | Hosts
The Cloud platform type property is added to the host properties page for Kubernetes, OpenShift, and Cloud Foundry hosts.
Infrastructure Monitoring | Hosts
The Region relation property is now available for the OpenStack hosts on the host properties page.
Infrastructure Monitoring | Hosts
On the host page, the following charts are now available in the host performance chart group:
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.
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.
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.
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.
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.
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.
To learn about changes to the Dynatrace API in this release, see Dynatrace API changelog version 1.262.
The 1.262 GA release contains 10 resolved issues.
This is a cumulative update that contains all previously released updates for the 1.262 release.
This is a cumulative update that contains all previously released updates for the 1.262 release.