Dynatrace Managed release notes version 1.172

New features and enhancements

Receive notifications when your quota of Digital Experience Monitoring (DEM) units runs low

We want to make sure that monitoring of your applications’ digital experience isn’t stopped due to your license running short of DEM units. Dynatrace Managed now notifies you when you’ve consumed 90% of your licensed DEM unit quota. With this approach, your cluster administrator can pro-actively adjust your licensed monthly or annual DEM unit quota. See example notification below, stating that 90% of the allotted DEM units have been consumed

Once the quota limit is reached, the notification changes, letting you know that DEM has been disabled:

Once the quota has been adjusted, notifications for all affected users are removed automatically. Note that these notifications are only triggered for DEM licenses. Notifications for other monitoring unit types, such as host units, custom metrics, and Log Analytics, will be added in future releases.

Configuration changes are now listed in audit log files

Transparency and traceability of configuration changes are key to managing large Dynatrace installations and enabling multiple teams to collaborate effectively. Dynatrace provides a set of audit logs that help you understand all configuration changes that have been made to each Dynatrace cluster.

Dynatrace Managed already exposes configuration changes via the Cluster Management Console. As of version 1.172, all changes made to a cluster configuration or an environment setting are stored to an audit log file. This enables processing by log management tools or automated scripts so that proper notifications can be set up.

Audit logs are stored at the cluster nodes where system changes are executed. To see the complete picture of all changes that have occurred across all nodes, you need to process audit logs from all nodes. Audit logs are available on individual nodes at DATASTORE_PATH/log/server.

In Dynatrace Managed 1.172, we introduce yet another set of audit logs: Configuration changes. See the audit log example below that shows a change of maintenance window:

audit.config.change.0.0.log

2019-06-20 04:49:09 UTC {"eventType":"CONFIG_UPDATE","tenantId":"xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx","userId":"unknown","userIdType":"USER_NAME","userOrigination":"unknown","sessionId":null,"identity":"ConfigIdentifier{configType=ONPREM_AUTOMATIC_UPDATES, identifier=ONPREM_AUTOMATIC_UPDATES}","identityCategory":"CONFIG_UPDATE","success":true,"timestamp":1561006149672,"message":"{\"jsonPatch\":\"[{\\\"op\\\":\\\"replace\\\",\\\"path\\\":\\\"/scheduledAutomaticUpgradeTime\\\",\\\"value\\\":1561006149661}]\"}"}

Audit logs open up a whole new set of use cases for custom notifications with log monitoring tools. We’ll describe some of these use cases in an upcoming blog post.

Improved cluster resilience and lower disk space requirements

Dynatrace can optimize the processing of monitored data to improve scaling, automatically control performance of OneAgents, or enable new features when all running OneAgents versions are capable of supporting them. From now on, Dynatrace will independently adjust its configuration to enable these features.

Based on OneAgent activity for the past 30 days, the configuration is adjusted for each monitoring environment that runs on your cluster. Additionally, OneAgent installation packages that are no longer in use will be removed and the disk space will be freed up (which means that earlier OneAgent versions won’t be able to connect or send data).

Other improvements

See additional steps required for manual update to Dynatrace Managed version 1.172.

All new features introduced with Dynatrace SaaS version 1.171 and version 1.172 are now also supported by Dynatrace Managed.

Resolved issues