Dynatrace Managed release notes version 1.230

Dynatrace news

New features and enhancements


  • Reduce Elasticsearch backup snapshots retention to 5 days. Old snapshots will be automatically removed after the upgrade.
  • Problems API v2 now includes event evidence data as part of the event details.
  • With this release, svchost.exe is excluded from injection. This eliminates certain timeout issues with Windows Server 2019 at boot.
  • You can now clone a service-level objective (SLO) by selecting More () > Clone SLO in the Actions column of the Service-level objectives page. This opens the **Add new SLO ** page already filled in with the settings from the cloned SLO.
  • Service-level objectives are now management zone–aware. The Service-level objectives page is filtered by management zones selected in the global filter for management zones. You can see only the SLOs that belong to the management zones you have access to, or to SLOs that belong to no management zone. An SLO belongs to a management zone by adding the management zone name or ID in the Entity selector. This also affects the Service-level objectives tile in the dashboard where you can only see data for the Service-level objectives that belong to management zones you have access to. Otherwise, an “Access denied” message will be shown on the tile instead.
  • Custom events for alerting using the Build tab and advanced query mode now apply the same metric dimension limits that are applied to Code-tab-based configurations.
  • Outage-handling settings of browser monitors and HTTP monitors can now be managed via the Settings API. As a result, it’s now possible to set a default for outage-handling settings at the environment level for all browser monitors or all HTTP monitors. You can override these at the monitor level.
  • Real user traffic has been added to the world map on the browser monitor details page.
  • Prometheus metrics from exporters in Kubernetes that aren’t running on a OneAgent-monitored node now consume DDUs.
  • Events API v2 has been updated.
  • The Kubernetes monitoring pages for workloads and pods are extended with a new log card that shows the Kubernetes logs. Note that Log monitoring must be enabled.
  • Charting of timeslots in service data–related pages like multidimensional analysis has been unified with Data explorer.

Local self-monitoring metrics

A newly created environment for purely self-monitoring purposes is created on the cluster. It aggregates self-monitoring metrics from all environments in the cluster. The self-monitoring environment is named Local-Self-Monitoring. It is excluded from all usage consumption and does not contribute to the monitoring consumption. You cannot connect any OneAgents, ActiveGates, Extensions nor set up Synthetic monitoring in the environment. See, Local self-monitoring environment. More details will come in a separate blog post, shortly.

Metrics API: dimension keys

The Metrics API v2 no longer supports legacy dimension keys in metric selectors. Use dt.entity.<entity_type>, not <entity_type>. For example, for a host dimension, use dt.entity.host, not Host. For more information, see Metric ingestion protocol.

The post Dynatrace Managed release notes version 1.230 appeared first on Dynatrace blog.

Dynatrace Managed release notes version 1.230