Dynatrace Managed release notes version 1.232
These release notes relate to Dynatrace Managed specific changes. To learn about general Dynatrace changes included in this Dynatrace Managed release, see:
- Dynatrace SaaS release notes version 1.232 and Dynatrace SaaS release notes version 1.231
- Dynatrace API changelog version 1.232 and Dynatrace API changelog version 1.231
- Dynatrace OneAgent release notes version 1.231
New features and enhancements
- Log Monitoring API v2
/logs/search
response change: each element's value in theadditionalColumns
structure is now an array of strings rather than just a string. - The Service-level objectives (SLO) wizard has been redesigned:
- All input fields are on one page with three expandable sections to define an SLO.
- A new preview section enables you to test the definition iteratively against actual values before creating the SLO.
- Removed seven-day preview from create/edit custom event for alerting pages.
- Redesigned "Maintenance windows" page to take advantage of Settings 2.0.
- Custom service detection settings have been moved to Settings > Service detection in preparation for Settings 2.0 conversion of rule-based service detection settings.
- The application Health check page (from the application overview page, select More (…) > Health check) now has a checklist to quickly highlight configuration-induced issues that could prevent RUM data from being received.
- The display ID of a problem is now sent as an additional property for ServiceNow event notifications in the field
problem_displayId
. - Creating an SLO, if you are not an admin, now requires adding the proper management zone filter in the entity selector, where you have to add a management zone for which you have write access. If you do not have tenant-wide permissions, you can access the SLO settings page and see the SLOs that belong to management zones to which you have access, and you can edit the SLOs that belong to management zones to which you have write access.
- Dynatrace Hub recommendations added to Kubernetes details page for OpenShift clusters.
- On the Service-level objectives page, the Actions > Edit SLO entry has been renamed SLO definition. It opens the corresponding SLO on the Service-level objective definitions page, where you can view or edit the SLO definition (depending on your permissions).
- Improved load time of Dynatrace Managed web UI in case of problems with connection to Mission Control.
- Calculated app, log, and service metrics now consume Davis data units (Metrics pool).
- Dynatrace Community related settings are renamed to Support resources and live chat.
New version of Log Monitoring support for Dynatrace Managed
With Dynatrace Managed version 1.232, the new version of Log Monitoring is available. You can enable the latest version of Dynatrace Log Monitoring using cluster API. See Enable Log Monitoring for details.
The following Dynatrace components are required to fully benefit from the Log Monitoring Classic :
- Dynatrace Managed version 1.232+
- Dynatrace OneAgent version 1.217+
With Log Monitoring Classic , you have a new way to:
- Acquire log data - Generic log ingestion (Logs Classic)
- Analyze log data - Log viewer (Logs Classic)
- Alert on log data - Log metrics (Logs Classic)
- Define custom index log data attributes for log data that is ingested - Log custom attributes (Logs Classic)
- Create log events based on log data and use them in problem detection - Log events (Logs Classic)
New Mission Control communication endpoints
We've updated our network requirements for the outbound communication from a Dynatrace Managed cluster to Dynatrace Mission Control. There are two new IPs: 46.137.81.205
and 52.48.91.146
, and three new domains:
mcsvc-us.dynatrace.com
, mcsvc-eu.dynatrace.com
, mcsvc-ap.dynatrace.com
.
They will be used to transmit health checks, license updates, software updates etc. We recommend to update your firewalls to the updated list - this will allow to better utilize Mission Control endpoints. Existing cluster deployments utilize the communication endpoint without any changes. For new deployments please make sure to:
- Update your firewall
- Plan new deployments, new cluster nodes in network that allow to connect to Mission Control to all IPs/endpoints.
See updated Outbound Communication to Dynatrace Mission Control.
Resolved issues
- General Availability (Build 1.232.99)
- Update 101 (Build 1.232.101)
- Update 104 (Build 1.232.104)
- Update 108 (Build 1.232.108)
- Update 110 (Build 1.232.110)
- Update 112 (Build 1.232.112)
- Update 114 (Build 1.232.114)
General Availability (Build 1.232.99)
The 1.232 GA release contains 76 resolved issues (including 4 vulnerability resolutions).
Component | Resolved issues |
---|---|
Application Security | 2 |
Cluster | 69 (4 vulnerabilities) |
Cluster Management Console | 4 |
Infrastructure monitoring solution | 1 |
Application Security
- Improved the vulnerabilities table to resolve issue in which details could not be viewed for some security problems. (CASP-11916)
- Removed the "Show all process groups" button in the "Affected Process Groups" pane of the "Security overview" page. (CASP-12511)
Cluster
- Vulnerability: In response to CVE-2021-44228 and CVE-2021-45046, applied the recommended mitigation measures of removing `org/apache/logging/log4j/core/lookup/JndiLookup.class` from the Log4j library. (APM-342160)
- Vulnerability: In response to CVE-2021-44832, CVE-2021-45105, CVE-2021-44228 and CVE-2021-45046, applied the recommended mitigation measures of updating the log4j library to the latest version 2.17.1. In Premium HA installations log4j update will take place in near future. (APM-345946)
- Vulnerability: Updated Log4j in Elasticsearch client to version 2.17.1. (APM-345471)
- Vulnerability: In response to CVE-2021-44228 (Log4j vulnerability), JVM parameters have been extended for Dynatrace Server and Elasticsearch. (APM-341605)
- "Data explorer" metric selector list no longer persists after browser back button is selected. (APM-331871)
- Geolocation lookup problem related to IPv6 addresses has been corrected. (APM-332776)
- Improved cluster detection in root cause analysis. (APM-332992)
- Resolved issue causing high CPU load on cluster and partly missing host unit calculation. (APM-337680)
- Process group monitoring overrides now work correctly for new settings. (APM-337269)
- False-positive monitoring alerts caused by internal communication timeouts have been eliminated. (APM-337001)
- Improved validation to prevent pinning "Problems" tile to dashboard when filters are invalid. (APM-333569)
- Fixed an issue with the active in-memory event limit (expected limit not reached). (APM-329683)
- Added REST API endpoint that can be called to set new cluster log events per minute limit based on available resources. (APM-341433)
- Corrected inconsistency between tags in ServiceNow event notifications and tags of the event when the tags changed on the affected entity of the event after event creation. (APM-332637)
- Improved auto-detection of 1st-party resources. (APM-333042)
- Kubernetes workload and pod details pages no longer crash when user doesn't have `View logs` permission. (APM-337632)
- Removed "Access tokens" entry from the Dynatrace menu for users who don't have sufficient permissions. (APM-335213)
- Resolved issue causing server error during fetch of dashboard tile data. (APM-331846)
- Display name change of metric dimension is now correctly propagated to "Metrics" and "Data explorer" pages. (APM-333774)
- Navigation to "Kubernetes workloads" page now correctly handles clusters with special characters in the name. (APM-334030)
- "Server overloaded" popup message no longer displayed on larger deployments. (APM-339014)
- User session date-related filters now yield correct query results. (APM-329731)
- Log queries using comparison operators like `<` and `>` are now correctly rejected as unsupported. (APM-329649)
- Split time series are now aggregated on autogenerated charts on unified analysis page. (APM-340244)
- Resolved issue that prevented filtering "Node analysis" page with key-only labels. (APM-334323)
- The "Log query table" dashboard tile now supports multi-slice search API calls. (APM-325844)
- Fixed occasional inconsistency between filtering by OneAgent version running on hosts and the value displayed for hosts on the "Deployment status" page. (APM-336403)
- Corrected spelling of entity technologies `IBM_WEBSPHERE_APPLICATION_SERVER` and `IBM_WEBSPHERE_LIBERTY`. (APM-338245)
- Disabled sorting on "Kubernetes workloads" page, "Pods" column, when the shown entity limit is reached. (APM-334052)
- Fixed a bug that prevented updating Session Replay privacy settings from REST API. (APM-345827)
- Restored support for CentOS Stream 8. (APM-341686)
- Fixed an issue in which the Client IP of an AWS Lambda invoked via API Gateway and monitored with OneAgent for AWS Lambda (Python, Node, Java) was additionally redundantly displayed as proxy IP. (APM-325810)
- Azure VMs that are monitoring candidates are now labeled "no OneAgent" on the Azure region and scale set pages. (APM-323431)
- Improved baselining alert sensitivity for Settings 2.0 configurations to ensure appropriate alerting. (APM-341879)
- "Data explorer" time formatting improved to show days. (APM-333920)
- Capitalized filter values are now correctly parsed. (APM-338476)
- Disabled extension preview on big tenants (over 1,000 PROCESS_GROUPS) to avoid performance issues. (APM-333310)
- Fixed a bug with the setting "Mask user actions (web applications only)" for browser extension injected applications. (APM-337861)
- When a request filter is active on browser monitor multidimensional analysis, text is displayed during calculated metric creation to warn that the request filter is ignored for the created metric. (APM-335916)
- Improved performance of Kubernetes cluster details page when Events API v2 is enabled. (APM-335805)
- Navigating to a different browser monitor using the global search bar now properly reloads the new browser monitor details page. (APM-329912)
- Adjusted wording of test results for "Problem notifications" integrations to state which type of notification was tested. (APM-336298)
- When opening a public dashboard link while already logged in, the dashboard's default management zone and timeframe are now respected. (APM-335500)
- Improved messaging for access token generation when user has insufficient permissions. (APM-338100)
- Resolved issue that made problem details page inaccessible for affected problems. (APM-338039)
- Legend on "Data explorer" pie chart visualization now correctly reacts to changes in "Show legend" setting. (APM-335899)
- Custom services API - lack of `annotations` parameter no longer breaks validation. (APM-336854)
- Corrected issue with tile threshold configuration in dashboards created using API. (APM-338146)
- Fixed issue that caused validation errors when using timeframe-based Problems API v2 endpoints in conjunction with certain relative UI timeframes. (APM-331590)
- Improved behavior of color selector for "Data explorer" thresholds. (APM-337840)
- Resolved issue in which custom metrics created in the last 10 seconds of a minute and data written in those 10 seconds could return different data for minute resolution than for higher resolutions after 1 or more hours. (APM-335710)
- Date and time are now determined and displayed consistently across user sessions, session details, and user details pages. (APM-337538)
- Fixed a display issue on the problem details page that truncated the linked problem text. (APM-330540)
- Added validation to prevent crashes in certain tables when they do not have a threshold configured. (APM-334768)
- Timeframe selector for "Data explorer" now working correctly. (APM-340320)
- Corrected an issue with process group monitoring overrides. (APM-339558)
- Management zone rules can no longer be created via the REST API with an entity selector that would result in entity types that don't support management zones. (APM-334401)
- Multidimensional analysis filter now allows multiple request attribute filters applied from dimension splitting. (APM-334220)
- Fixed an issue in which some users received "403 Forbidden" error on attempt to access Anomaly Detection pages. (APM-341698)
- Improved request error capturing with HTTP status codes. (APM-338028)
- Resolved issue in "Data explorer" in which splitBy information was dropped when a filter condition was added to a query. (APM-332819)
- Fixed an issue that caused reading of invalid container monitoring configuration in some cases. (APM-339100)
- The OpenAPI documentation of the Dynatrace Events REST API v2 now includes the response structure of its ingest endpoint. (APM-333568)
- Fixed an issue in which the Kubernetes detail page crashed with a 403 status code for management zones users. (APM-341209)
- Resolved issue with enabling/disabling container monitoring for BPM, Containerd, CRI-O, and Winc. (APM-337609)
- Improved handling of preset dashboards in dashboard JSON editor: presets can now be edited by their non-admin owners in the editor, and an error message is now shown when a non-admin tries to publish or unpublish a preset in the editor. (APM-335491)
- Fixed an issue that resulted in a technical difficulties page for some users when submitting or cancelling problem feedback. (APM-330548)
- Resolved issue in which a user with only write settings permission for a management zone containing HTTP monitors couldn't duplicate a HTTP monitor via the synthetic list. (APM-337735)
- Toggling "Show legend" for a table tile no longer removes thresholds. (APM-333052)
Cluster Management Console
- Data ingested via Log Monitoring v2 is no longer included by default in backup to avoid overconsumption of resources. (APM-336489)
- Corrected proxy certificate import issue. (APM-341894)
- Resolved issue in which, when using REST API to modify permissions for a given group to selected environments and management zones, all of that group's other permissions were cleared for all environments and management zones. (APM-338188)
- Resolved issue in which, if there was no configuration of permissions to management zones for a given user group, it was impossible to create this configuration via public REST API. (APM-339033)
Infrastructure monitoring solution
- Unmounted/inaccessible VMware datastores no longer raise alerts about no free space left. (APM-333006)
Update 101 (Build 1.232.101)
This cumulative update contains 1 resolved issue and all previously released updates for the 1.232 release.
Cluster
- Resolved issue causing error when adding a new "Single value" tile from the dashboard editor. (APM-346198)
Update 104 (Build 1.232.104)
This is a cumulative update that contains all previously released updates for the 1.232 release.
Update 108 (Build 1.232.108)
This cumulative update contains 4 resolved issues and all previously released updates for the 1.232 release.
Component | Resolved issues |
---|---|
Application Security | 1 |
Cluster | 3 |
Application Security
- Resolved a problem with internal consistency check for detecting duplicate copies of Security Problems in ElasticSearch, which lead to false consistency warning messages. (CASP-12903)
Cluster
- Resolved an issue that was causing alerts for infrastructure (for example, Host CPU) to be generated even when disabled. (APM-348563)
- Fixed a bug where some entitySelector queries lead to empty results, depending on the order of the filters. (APM-350114)
- Description placeholder substitution is now correct for custom event configurations. (APM-349779)
Update 110 (Build 1.232.110)
This cumulative update contains 2 resolved issues and all previously released updates for the 1.232 release.
Component | Resolved issues |
---|---|
Cluster | 1 |
Cluster Management Console | 1 |
Cluster
- Fixed a bug that resulted in missing information in the Dynatrace web UI Problems and problem notifications. (APM-348206)
Cluster Management Console
- Upgrade log4j to v2.17.1 for Premium High Availability. (APM-346554)
Update 112 (Build 1.232.112)
This cumulative update contains 3 resolved issues and all previously released updates for the 1.232 release.
Component | Resolved issues |
---|---|
Application Security | 1 |
Cluster Management Console | 2 |
Application Security
- Resolved security monitoring rule issue (property "Management zone" was evaluated incorrectly) that caused vulnerabilities to continuously toggle between `OPEN` and `RESOLVED` states. (CASP-13279)
Cluster Management Console
- Upgrade log4j to v2.17.1 for Premium High Availability. (APM-346554)
- Fixed potential migration for the latest index, which in some corner cases could lead to an invalid problem state. (APM-351245)
Update 114 (Build 1.232.114)
This cumulative update contains 2 resolved issues and all previously released updates for the 1.232 release.
Component | Resolved issues |
---|---|
Cluster | 1 |
Cluster Management Console | 1 |
Cluster
- Resolved an issue where metric data would be incorrectly or only partially displayed when a metric was ingested with a monitored entity dimension. (APM-352822)
Cluster Management Console
- Resolved caching issue on REST endpoint `/api/v1.0/onpremise/groups/managementZones`, which caused updates to fail for recently created management zones. (APM-352475)