Dynatrace SaaS release notes version 1.297
Rollout start: Jul 29, 2024
Product news
- Break the silos: Enrich vulnerability findings with runtime contextļ»æ
Dynatrace delivers cross-container-registry security findings, visibility, orchestration, and prioritization.
- Collaborate with peers in hunting security threatsļ»æ
In the dynamic world of security investigations, efficient collaboration can make all the difference. Today, we're thrilled to announce that Dynatrace has enabled case sharing in the Security Investigator app, which will transform how professionals conduct collaborative investigations.
Breaking changes
DavisĀ® Analyzer response change
Platform | Davis
The execution logs in the DavisĀ® Analyzer response no longer contain the analyzer name. You can find the analyzer name in the URL when calling the analyzer via API.
New features and enhancements
Unified ingest supports OCSF 1.1.0 vulnerability findings
Platform | OpenPipeline Application Security | Vulnerabilities
Data in Open Cybersecurity Schema Framework (OCSF) 1.1.0ļ»æ format can now be automatically mapped to the Semantic Dictionary conventions once ingested into Grail via our built-in security events endpoint.
For details, see Ingest vulnerability findings in OCSF format.
Dashboard tile-specific timeframes
In Dashboards, you can now add a tile-specific timeframe to a tile.
This timeframe overrides the dashboard timeframe set in the upper-right corner of the dashboard. Using this method, a dashboard can have multiple tiles, where each tile has its own timeframe.
For details, see Use dashboards.
Matcher for the origin of the log source
Infrastructure Observability | Log Monitoring
The new matcher indicates the origin of the log source, highlighting which detector among IIS, open file, system detector or custom file configuration was used by the OneAgent to discover the log file. It is available for all configuration screens with OneAgent version 1.295+.
Process request count metric on Grail
Infrastructure Observability | Processes
Use the metric dt.process.request_count to learn the HTTP(s) request count for processes. The metric is available on Linux only.
Request app installation
Dynatrace Hub
Users without permission to install Dynatrace Apps can now automatically request their admins to install an app directly from the Hub. After a user requests the app installation, an admin receives an email. The automatic email notification works only after the environment admin configures the responsible admins in the Hub settings. For details, see Dynatrace Hub apps installation.
Dynatrace API
To learn about changes to the Dynatrace API in this release, see Dynatrace API changelog version 1.297.
Dynatrace SaaS resolved issues
General Availability (Build 1.297.34)
The 1.297 GA release doesn't contain any user-facing resolved issues.
Update 38 (Build 1.297.38)
This is a cumulative update that contains all previously released updates for the 1.297 release.
Update 40 (Build 1.297.40)
This is a cumulative update that contains all previously released updates for the 1.297 release.
Update 43 (Build 1.297.43)
This is a cumulative update that contains all previously released updates for the 1.297 release.
Update 45 (Build 1.297.45)
This is a cumulative update that contains all previously released updates for the 1.297 release.
Update 48 (Build 1.297.48)
This cumulative update contains 16 resolved issues and all previously released updates for the 1.297 release.
| Component | Resolved issues |
|---|---|
| Dynatrace Cluster | 13 |
| Synthetic Monitoring | 1 |
| User interface | 1 |
| Session Replay | 1 |
Dynatrace Cluster
- If your OneAgents can connect to the target environment only via Environment ActiveGate (for example, they are in a restricted network), then they can't use Remote Configuration Manager to modify their connection. (DMX-7911)
- Maintenance window evidence no longer contributes to entities being marked as root causes of a problem. A maintenance window alone does not indicate a root cause but rather provides additional information. (DI-15158)
- Limits to monitored entities instances are now applied after filtering out temporary services. (DI-15252)
- Fixed an issue where writing to setting `builtin:host.monitoring` could cause a general server slowdown. (PS-25419)
- Resolved issue ignoring Full Stack billing for traces ingested via EEC and causing DDU consumption instead. (TI-13561)
- Failure Analysis resets to last 2 hours when loading unknown events instead of crashing. (TI-13226)
- Changed the parameter `credentialsEnabled` to optional and provided default value `true`. (PCLOUDS-4658)
- Resolved an issue that caused events to merge in the same problem even if merging was disabled for one of the events. Fixed incorrect merging of events suppressed by a maintenance window with the new event, which prevented new problems from opening after the maintenance window ended. (DI-15343)
- Added a new binary `runc` in the important processes list to avoid noise on the Process list in containerized environments. (HOST-6207)
- Fixed retrieval of RDS and TransitGateway infrastructure and metrics for customers with large amounts of instances. (PCLOUDS-4416)
- Fixed an issue that caused Foundation & Discovery agents to lose connectivity for some time after a server restart. (LIMA-20052)
- Implements optional SHA-1 validation for ingest messages, in order to reliably detect corrupted data & trigger retries on the caller side. (GRAIL-30014)
- Fixed incorrect spelling in cookie schema. (RUM-20437)
Synthetic Monitoring
- In case of a global outage (a problem with the Synthetic engine or network, missing data/result), an already open problem will time out, so anomaly detection operates only on up-to-date data. (SYNTH-12287)
User interface
- Fixed the `ports` property formatting for Process group instances. (TI-13289)
Session Replay
- Fixed an issue that broke the replay and showed a blank screen instead. (SR-5732)
Update 53 (Build 1.297.53)
This cumulative update contains 7 resolved issues and all previously released updates for the 1.297 release.
| Component | Resolved issues |
|---|---|
| Dynatrace Cluster | 6 |
| Synthetic Monitoring | 1 |
Dynatrace Cluster
- Resolved issue ignoring Full Stack billing for traces ingested via EEC and causing DDU consumption instead. (TI-13561)
- Fixed an issue where writing to setting `builtin:host.monitoring` could cause a general server slowdown. (PS-25419)
- Changed the parameter `credentialsEnabled` to optional and provided default value `true`. (PCLOUDS-4658)
- Fixed an issue that caused Foundation & Discovery agents to lose connectivity for some time after a server restart. (LIMA-20052)
- Fixed an issue where offline PGIs were still considered for monitoring and usage. (RSA-17167)
- Fixed an issue where PGIs excluded from monitoring were generating usage. (RSA-17259)
Synthetic Monitoring
- In case of a global outage (a problem with the Synthetic engine or network, missing data/result), an already open problem will time out, so anomaly detection operates only on up-to-date data. (SYNTH-12287)