Starting with Dynatrace OneAgent and ActiveGate version 1.231, we are upgrading the Extension Framework (also referred to as the plugins framework) from Python 3.6 to Python 3.8.
Consequences: Some Dynatrace extensions running in your environment may stop working and require redeployment of a new version prepared for Python 3.8.
Symptoms:
No data is provided for affected metrics on dashboards, alerts, and custom device pages populated by the affected extension metrics.
Extension logs display errors. Most often this will manifest itself as Python ModuleNotFoundError in the PluginAgent log.
Sometimes the Python virtual machine crashes.
Impact: This issue affects only those extensions that use native libraries called from Python code distributed with the extension.
In Dynatrace Hub, find and select one of the extensions listed to the left.
On the extension details page, select Download to download the extension ZIP file to your machine. If there are operating system options, be sure to select the correct download for your deployment.
Deploy the extension per the instructions on the corresponding documentation page. (In the list to the left, select the name of the extension.)
For assistance, contact a Dynatrace product expert via live chat within your Dynatrace environment.
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).
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 can edit the SLOs that belong to management zones to which you have write access.
Infrastructure Monitoring
Dynatrace Hub recommendations added to Kubernetes details page for OpenShift clusters.
Problem detection and notifications
Removed seven-day preview from create/edit custom event for alerting pages.
Redesigned Maintenance windows page to take advantage of Settings 2.0.
Settings security policies
A new condition for security policies has been added that allows you to grant access to settings selectively to a single host group or hosts within this host group. Read more about it in the IAM services reference.
These pages are now available to be used in security policies:
Settings > Anomaly detection > Applications
Settings > Anomaly detection > Services
Settings > Anomaly detection > Database services
Settings > Anomaly detection > Infrastructure
Settings > Anomaly detection > Extension events
Settings > Anomaly detection > Custom events for alerting
To see all queues and topics detected by OneAgent within your monitoring environment
Go to Message Queues.
Select a specific queue or topic to display details about its connected producer and consumer services, as well as technology-specific metrics. Details are available for ActiveMQ, Apache Kafka, IBM MQ, RabbitMQ, and Tibco EMS.
User session date-related filters now yield correct query results. (APM-329731)
Application Security
Improved the vulnerabilities table to resolve issue in which details could not be viewed for some security problems. (CASP-11916)
Dynatrace API
The OpenAPI documentation of the Dynatrace Events REST API v2 now includes the response structure of its ingest endpoint. (APM-333568)
Infrastructure Monitoring
Disabled sorting on "Kubernetes workloads" page, "Pods" column, when the shown entity limit is reached. (APM-334052)
Unmounted/inaccessible VMware datastores no longer raise alerts about no free space left. (APM-333006)
Log Monitoring
Log queries using comparison operators like `<` and `>` are now correctly rejected as unsupported. (APM-329649)
Problem detection and notifications
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)
Fixed an issue with the active in-memory event limit (expected limit not reached). (APM-329683)
Improved validation to prevent pinning "Problems" tile to dashboard when filters are invalid. (APM-333569)
Fixed issue that caused validation errors when using timeframe-based Problems API v2 endpoints in conjunction with certain relative UI timeframes. (APM-331590)
Synthetic monitoring
Navigating to a different browser monitor using the global search bar now properly reloads the new browser monitor details page. (APM-329912)
User interface
Navigation to "Kubernetes workloads" page now correctly handles clusters with special characters in the name. (APM-334030)
"Data explorer" metric selector list no longer persists after browser back button is selected. (APM-331871)
Display name change of metric dimension is now correctly propagated to "Metrics" and "Data explorer" pages. (APM-333774)
Removed "Access tokens" entry from the Dynatrace menu for users who don't have sufficient permissions. (APM-335213)
Cluster
Geolocation lookup problem related to IPv6 addresses has been corrected. (APM-332776)
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)
Disabled extension preview on big tenants (over 1,000 PROCESS_GROUPS) to avoid performance issues. (APM-333310)
Azure VMs that are monitoring candidates are now labeled "no OneAgent" on the Azure region and scale set pages. (APM-323431)
Added validation to prevent crashes in certain tables when they do not have a threshold configured. (APM-334768)
Fixed an issue that caused reading of invalid container monitoring configuration in some cases. (APM-339100)
False-positive monitoring alerts caused by internal communication timeouts have been eliminated. (APM-337001)
Fixed an issue that caused reading of invalid container monitoring configuration in some cases. (APM-339100)
Update 205 (Build 1.231.205)
This is a cumulative update that contains all previously released updates for the 1.231 release.
Update 208 (Build 1.231.208)
This is a cumulative update that contains all previously released updates for the 1.231 release.
Update 210 (Build 1.231.210)
This cumulative update contains 1 resolved issue and all previously released updates for the 1.231 release.
Application Security
Removed the "Show all process groups" button in the "Affected Process Groups" pane of the "Security overview" page. (CASP-12511)
Update 219 (Build 1.231.219)
This cumulative update contains 1 resolved issue and all previously released updates for the 1.231 release.
Cluster
Corrected issue with process group monitoring overrides. (APM-339558)
Update 223 (Build 1.231.223)
This cumulative update contains 1 resolved issue and all previously released updates for the 1.231 release.
Cluster
Fixed an issue in which the Kubernetes detail page crashed with a 403 status code for management zones users. (APM-341209)
Update 232 (Build 1.231.232)
This cumulative update contains 1 resolved issue and all previously released updates for the 1.231 release.
Cluster
Fixed an issue in which some users received "403 Forbidden" error on attempt to access Anomaly Detection pages. (APM-341698)