Metric expressions help you create actionable insights to meet the needs of disparate SRE, DevOps, and business teams.
Dynatrace extends its Real User Monitoring capabilities to enhance mobile-app user experience with easier and faster crash analytics.
The new Data explorer makes it easy to calculate metrics that deliver more relevant and actionable dashboard insights for IT and business teams.
Dynatrace Managed now compresses transaction data that's older than three days and includes improvements to Adaptive Data Retention ADR).
Dynatrace provides automatic and intelligent observability for all telemetry data in one platform. Today, we’re further expanding our open platform with OpenTelemetry trace ingest. This new capability allows for the ingestion of distributed traces from any third-party source that emits OpenTelemetry trace data. This enables organizations to ensure end-to-end observability insights for heterogeneous cloud-native environments.
Data Explorer is now in GA release and is the recommended Dynatrace charting tool.
If you have custom charts:
OpenTelemetry trace ingest is now in GA release. For more information, see OpenTelemetry and Dynatrace.
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.
Events that were created during a maintenance window that suppresses problem creation are now shown in the event pages and are available through the Events API.
You can now tag the AWS DynamoDB tables using automated, rule-based tagging.
You can now define custom security-monitoring rules for Application Security.
Successful browser monitor visits without user actions now write availability data and are billed accordingly.
Ingestion of custom Davis events now results in the consumption of Davis data units because they require more processing and analytical power than built-in event ingestion. Events that impact DDU consumption are marked in the Dynatrace web UI on the configuration page (Settings > Log Monitoring > Events extraction) and in API documentation.
Custom traces are licensed on the basis of ingestion of spans (a span is a single operation within a trace). Spans ingested via the Dynatrace Trace API consume DDUs.
The overview pages for Kubernetes namespaces, workloads, and pods now offer a customizable unified analysis view that collects all relevant information regarding namespaces, workloads, and pods in one place.
To learn about changes to the Dynatrace API in this release, see Dynatrace API changelog version 1.222.
The 1.222 GA release contains 19 resolved issues.
This cumulative update contains 1 resolved issue and all previously released updates for the 1.222 release.