Dynatrace SaaS release notes version 1.280
Rollout start: Nov 29, 2023
Want to ask questions or give feedback? Head over to Dynatrace Community.
Announcements
Mainframe Monitoring with DPS
Application Observability | Mainframe
Dynatrace Mainframe Monitoring provides automatic end-to-end application performance monitoring for transactions, regions, and apps deployed on IBM z/OS. It includes distributed tracing, metrics, topology, and code-level insight for 30+ supported technologies.
With the DPS capability for Mainframe Monitoring:
- You get flexibility in licensing for incremental monitoring rollouts (for example, you can start small and expand coverage over time).
- You only pay for the active monitoring period (for example, downtimes are not charged).
- You get cost transparency and budget management in Account Management.
For more details, see Mainframe Monitoring.
Log source and storage configuration upgrade
Infrastructure Observability | Logs
With the release of Dynatrace version 1.285 (March 2024), Dynatrace will automatically convert your log source and log storage configurations to the latest version.
You can also upgrade to the new configuration by selecting Upgrade configuration. All of your current settings will be fully upgraded.
The upgraded configuration (see Log ingest rules) defined on the Custom log source configuration and Log sources and storage pages will give you:
- Greater flexibility in defining log sources (for example, log path, log level, Kubernetes namespace, Kubernetes deployment)
- Flexibility in defining log sources (using environment, host group, and host scopes)
- Granularity in managing log source access rights
- Use of the REST API for managing log sources
- Ability to filter and mask log data at capture
Breaking changes
Settings REST API change: Host auto-injection
Breaking change Infrastructure Observability | Hosts
In the Dynatrace web UI, on the Host monitoring page for a selected host, the Auto-injection toggle has been moved from the Monitoring tab to the Advanced Settings tab and renamed to ProcessAgent injection.
- Go to Hosts or Hosts Classic (latest Dynatrace) and select the host that you want to configure.
- On the host details page, select
> Settings. - On the Host settings page, select Host monitoring.
- Select the Advanced Settings tab.
If you're using any automation tools to manage this setting and you're leveraging the Dynatrace API (for example, Dynatrace Configuration as Code via Monaco or Terraform), the auto-injection settings schema ID was renamed.
Before:
builtin:host.monitoring/autoInjection
After:
builtin:host.monitoring.advanced/processAgentInjection
You need to pull the new settings schemas and update the value. The old settings schema will be ignored.
Unified attribute privacy settings
Application Observability | Distributed traces
Breaking change
The Span attributes, Resource attributes, and Span events settings have been merged into the Attribute capturing settings.
The separation by attribute origin is replaced to make the privacy configuration simpler and clearer. Existing settings are automatically migrated and in case of duplicate attribute keys, only the most restrictive masking option is migrated. We recommend you verify your environment configuration for attribute-masking.
- Go to Settings.
- Select Server-side service monitoring > Attribute capturing.
- On the Attribute capturing page, perform the following actions.
- Select Allowed attributes to see the list of stored attributes key.
- Select Attribute data masking to verify the masking configuration for a stored attribute.
To learn more about attribute settings, see Attributes.
New features and enhancements
Aggregation functions available to use with DQL timeseries and makeTimeseries commands
Platform | DQL
Now you can use the following aggregations functions with timeseries and makeTimeseries commands:
sum,avg,min,maxwith timeseries commandsum,avg,min,max,count,countIfwith makeTimeseries command
New DQL functions
Platform | DQL
Now you can include the following functions in your DQL queries:
Peer certificate information hidden in execution details of HTTP monitors
Digital Experience | Synthetic Monitoring
You can opt to hide sensitive information from being displayed in the execution details of HTTP monitors via the Do not store and display request and response bodies and header values in execution details setting. Enabling this setting now also hides peer certificate information in the execution details.
Explore data in Notebooks
Latest Dynatrace Platform | Notebooks
Use the new UI-based experience to explore logs and metrics.
New metrics mathematical operations
Platform | DQL
It's now possible to perform mathematical operations between metrics using a combination of timeseries and fieldsAdd commands. To find out more, see this metrics on Grail example.
Log content size limit increased
Infrastructure Observability | Logs
The Event content maximum byte size (the maximum byte size that event content can contain) has been increased to 10 MB.
OS service monitoring events
Infrastructure Observability | Hosts
OS service monitoring events now also match the tags from the host entity where they originate.
New API to unblock auto-update
Infrastructure Observability | Hosts Infrastructure Observability | Deployment
Certain types of auto-update failures block further rollout of that version as a safety measure. A self-service API, /api/v1/oneagents/autoUpdateProblems, has been added to get and delete these problems to unblock an autoupdate rollout.
Kubernetes service ingress DNS names
Infrastructure Observability | Kubernetes
Kubernetes service ingress DNS names are now displayed on the Kubernetes service page. This is typically used in AWS load balancers.
Relevant field in Kubernetes API: service.status.loadBalancer.ingress.hostname
Attribute data privacy: Possibility to store all attributes by default
Application Observability | Distributed traces
You can now store all attributes by default.
Alerting profile property filter negation
Infrastructure Observability | Problems Infrastructure Observability | Alerting
Alerting profile property filters can now be negated, so an alert will not be triggered if an event of a problem matches the property filter.
Disk anomaly detection rule limit
Infrastructure Observability | Hosts
The maximum number of disk anomaly detection rules is now 1,000.
Custom-influenced Adaptive Traffic Management
Application Observability | Distributed tracing
You can set up traffic management rules for HTTP-based traffic. By customizing the contribution of specific transactions, you have better control of capturing within your environment's available trace volume and can immediately understand the capture rate of a specific service, (key) request, or result. To get started, see URL-based sampling. OneAgent version 1.279 is required to activate the rules.
Dynatrace API
To learn about changes to the Dynatrace API in this release, see Dynatrace API changelog version 1.280.
Resolved issues
General Availability (Build 1.280.103)
The 1.280 GA release contains 9 resolved issues.
| Component | Resolved issues |
|---|---|
| Dynatrace Cluster | 6 |
| Platform | 2 |
| Synthetic monitoring | 1 |
Dynatrace Cluster
- Corrected a Deployment page reference to point to the newly released Dynatrace Operator v0.14.1. (K8S-8042)
- Users without write access to OneAgent update settings can no longer select the "Update now" button to trigger a OneAgent update. (The button was incorrectly enabled; selecting it without the required permission resulted in a 403 error page.). (DMX-6248)
- Improved robustness of the classic problem list, which in rare cases could crash if you hover over the display ID of a problem with numerous details. (DAVIS-7086)
- Stuck navigation for distributed traces and MDA has been fixed. You can access the global MDA and distributed traces by selecting the first item in the breadcrumbs. (TI-9716)
- Resolved an issue in which, starting with OneAgent version 1.273, the cluster was no longer able to process nodes with ESB and messaging attachments with priority for the Enterprise Service Bus service, but instead resorted to displaying a simple messaging service. (OA-24051)
- The metric selector no longer allows the `:filter` operator without arguments. (CLUSTER-10442)
Platform
- Fixed an issue that could cause missing metric dimensions after changing a tenant's metrics dimensions storage index config. (CLUSTER-10355)
- Configuration API: Fixed an issue in which changing host monitoring settings via the deprecated `PUT /api/v1/hosts/{id}/monitoring` API reset the `autoInjectionEnabled` flag to its default value (enabled). (PS-11615)
Synthetic monitoring
- When the option not to store HTTP request sensitive data (i.e., request and response bodies and header values) is selected, peer certificate details are also hidden. (SYNTH-9132)