Dynatrace Managed release notes version 1.236

These release notes relate to Dynatrace Managed specific changes. To learn about general Dynatrace changes included in this Dynatrace Managed release, see:

New features and enhancements

Updated endpoints

We have updated endpoint documentation for creating and restoring Premium High Availability Elasticseach sections.

Completed product ideas

Improved assigning group permissions and policies to environments

Starting with Dynatrace Managed 1.236 we have improved filtering by adding the Doesn't have role filter option. Now you can filter for environments that do not have specified role.

For example the filter: Doesn't have role: Access environment will show environments that the group doesn't allow accessing at all. This is useful when you want to quickly find environments to grant missing permissions.

Operating systems support

    Current Dynatrace Managed operating systems support changes

    The following operating systems will no longer be supported starting 01 October 2024

    Past Dynatrace Managed operating systems support changes

    The following operating systems are no longer supported since 01 July 2024
    The following operating systems are no longer supported since 01 August 2024

    Resolved issues

    General Availability (Build 1.236.114)

    The 1.236 GA release contains 49 resolved issues.

    ComponentResolved issues
    Application Security2
    Cloud automation solution1
    Cluster42
    Cluster Management Console2
    RUM1
    Synthetic monitoring1

    Application Security

    • Security problems are no longer stuck in "EXPOSED" state when they are resolved but no more process groups are affected. (CASP-13400)
    • Inconsistent host coverage data, which can occur if software component reporting is enabled but the reported hosts are not ensured in Dynatrace, now only logs a warning (downgraded from throwing an exception) to avoid breaking the Application Security overview page. (APM-350518)

    Cloud automation solution

    • The SLO `timeframe` property (mandatory, used to create/update SLOs) was not present in the Swagger documentation with its respective example. It can now be found in the corresponding request body examples for POST /slo and PUT /slo. (APM-348140)

    Cluster

    • Fixed wording for database metrics in distributed traces: `Time spent in database calls` and `Calls to databases`. (APM-352627)
    • Fixed an issue where navigating to an entity screen for further analysis from a problem could lead to a 404. (APM-352778)
    • Corrected support for generic entity types in the Events API v2 and Problems API v2. (APM-349599)
    • Custom process group monitoring rule values are now correctly checked for illegal separator characters. (APM-347408)
    • Corrected "Other processes" value calculations in custom timeframes in host process list. (APM-349936)
    • Tenant CountryCode can be used to adjust IP and geolocation resolution based on political variations. When set to China, for example, Taiwan, Hong Kong, and Macao are resolved as regions within China rather than as countries in their own right. This resolves an issue where this was not applying for mobile visits. (RUM-4510)
    • Introduced a limit of 100,000 process group instances (last 72h) running on hosts presented on the "Deployment status" page for OneAgents. (APM-351868)
    • Fixed a bug that prevented users with write access to the `builtin:anomaly-detection.metric-events` schema from editing custom events for alerting. (APM-349748)
    • Kubernetes event date/time is now corrected to the current date/time if the received date/time is in the future due to a host/time issue. (APM-345661)
    • Fixed an issue in which "View PurePath" button on waterfall did not show up. (RUM-4285)
    • Request naming rules that use request attributes of type integer no longer cast the integer value to double. (APM-348343)
    • Elasticsearch high CPU utilization and slow down. (APM-355779)
    • Fixed an issue in which Kubernetes workload label and Kubernetes namespace label might be removed when going from a "Service health" tile on a dashboard to service list. (APM-352095)
    • In the "Data explorer" selecting the 'Single value' visualization type before running the query no longer results in an infinite "Loading..." message. (APM-353313)
    • A multidimensional analysis service filter with a request filter containing long database statements no longer results in clearing the filter due to invalid state. (APM-349729)
    • Fixed an issue, in which performance degradation happened on some settings write API requests. (APM-354058)
    • Added support for German umlauts in problem notification placeholder values. (APM-348640)
    • ActiveGates with cluster type are now also presented as suggestions for "ActiveGate used by host" filter type on the "Deployment status" page for OneAgents. (APM-346830)
    • Browser monitor data from IP addresses excluded in the RUM web application is now processed correctly. (APM-351730)
    • The "User sessions" page, "Application type" field, has been corrected to always show a value for each type, even when the value is 0%. (RUM-4375)
    • Corrected issue with maintenance window tag filters that led to them not matching their respective entity counterpart. (APM-350020)
    • Fixed, browser exclusion settings 2.0 that were shown for applications other than auto injected applications. (RUM-4394)
    • User ID breadcrumb is now correctly parsed and displayed on the user details page. (APM-347834)
    • Added missing diagnostic data for ActiveGate modules to the support archive generated from the Dynatrace web UI. (APM-352736)
    • Fixed an issue, in which service detection rules were applied incorrectly. (APM-358879)
    • Kubernetes service relations are now written correctly, even if a generic RUNS_ON relation was added. (APM-348647)
    • Corrected text formatting on "Disk Analytics Extension" page. (APM-349564)
    • After manual update of ActiveGate to a specific version via REST, the module update no longer fails. (APM-354104)
    • Fixed potential entity tag explosion on problems. (APM-351756)
    • 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)
    • Service request naming no longer uses invalid data for custom services. (APM-349598)
    • Fixed rare Elasticsearch index migration failure. (APM-347812)
    • Fixed an issue, which could cause the XHR Exclusion settings 2.0 conversion failure because of duplicate entries. (APM-358739)
    • Container and process lists are now displayed on the Kubernetes pod details page, also for PaaS deployments. (APM-352971)
    • Corrected data size calculation that prevented upload of iOS symbol files. (RUM-4323)
    • Fixed issue that extensions could not be uploaded via Hub UI for Dynatrace for Government (FedRAMP). (APM-349255)
    • Security problems that are resolved because of a monitoring rule change are now correctly added as resolved to the corresponding metric. (CASP-13112)
    • A 404 error no longer occurs when the user removes a tag on the ESXi host page. (APM-346125)
    • Fixed incorrect retaining time calculation in baselining over alerting prevention. (APM-356606)
    • Corrected management zone filtering for AWS. (APM-352410)
    • The namespace count for the Kubernetes cluster list is now synchronized with the count for the namespaces list. (APM-352162)
    • Fixed null pointer exception that occurred during evaluation for alerting on metric expressions. (APM-346741)

    Cluster Management Console

    • Support archive download timeout has been raised to 30 minutes. (APM-354595)
    • Resolved authentication failure when email domains were in uppercase for SAML integration in FedRAMP clusters. (APM-345209)

    RUM

    • Resolved parsing error involving brackets `()`, `{}`, and `[]` in the query builder in code mode. (APM-334179)

    Synthetic monitoring

    • Improved the behavior of opt-in panel: when closed, it is now minimized and put at the bottom of the page without the need to re-minimize it after page reload. (APM-355786)

    Update 118 (Build 1.236.118)

    This cumulative update contains 2 resolved issues and all previously released updates for the 1.236 release.

    Cluster

    • Opening an old problem can lead to an error page. (APM-357784)
    • Fixed incorrect retaining time calculation in baselining over alerting prevention. (APM-356606)

    Update 119 (Build 1.236.119)

    This is a cumulative update that contains all previously released updates for the 1.236 release.

    Update 122 (Build 1.236.122)

    This cumulative update contains 2 resolved issues and all previously released updates for the 1.236 release.

    Cluster

    • Fixed an issue that prevented browser and HTTP monitor creation in management zones using tag conditions. (APM-361639)
    • Elasticsearch high CPU utilization and slow down. (APM-355779)

    Update 123 (Build 1.236.123)

    This cumulative update contains 1 resolved issue and all previously released updates for the 1.236 release.

    Cluster

    • Improved metric selector filtering on entity names. (APM-363024)

    Update 130 (Build 1.236.130)

    This cumulative update contains 3 resolved issues and all previously released updates for the 1.236 release.

    ComponentResolved issues
    Autonomous Cloud1
    Cluster2

    Autonomous Cloud

    • When setting the optional Group parameter on the Kubernetes deployment page, the host group argument for the OneAgent is now set correctly. (K8S-1985)

    Cluster

    • Resolved issue with missing USQL query support for custom applications. It is now possible to filter custom applications with key user actions in USQL. (APM-362217)
    • Improved metric selector filtering on entity names. (APM-363024)