Dynatrace Managed release notes version 1.170

New features and enhancements

Cluster events audit logging

From a compliance perspective, audit traces are an absolute necessity. There are many legal concerns that must be adhered to, and audit logs serve as an official record that can be provided when an auditor asks for proof of compliance. Security is another area in which audit logs can be invaluable. 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.

Cluster event audit logs are available as of Dynatrace Managed version 1.170. See audit log example below:

audit.cluster.event.log

12019-05-29 09:29:42 UTC {"eventType":"CREATE","tenantId":"unknown","userId":"Cluster event service","userIdType":"SERVICE_NAME","userOrigination":"Cluster event (Internal)","sessionId":null,"identity":null,"identityCategory":"CLUSTER_EVENT","success":true,"timestamp":1559122182775,"message":"{\"clusterEvent\":{\"clusterEventType\":\"SERVER_LIFECYCLE\",\"timestamp\":1559122182775,\"summary\":\"Server 1 shutdown initiated.\",\"description\":\"ShutdownDescriptor [exitCode=0, caller=com.compuware.apm.server.core.ServerShutdownRunner, reason=Shutdown due to VM shutdown hook., restart=false, expected=true]\",\"userId\":\"com.compuware.apm.server.core.ServerShutdownRunner\",\"notification\":\"NONE\",\"clusterEventSeverity\":\"INFO\"}}"}

Additional audit log files will be made available in upcoming releases. Audit logs open up a whole new set of use cases for custom notifications using log monitoring tools. We’ll describe some of these use cases in an upcoming blog post.

Dynamic JVM memory settings update

Previously, to apply a RAM update on a cluster node host, you were required to perform an "in-place" upgrade or wait until the next scheduled upgrade. Starting with version 1.170, hardware updates are applied automatically when services are restarted. With this change, Dynatrace Managed deployment is now more resilient and more quickly adapts to your needs. To restart all services, run the following:

1/PRODUCT_PATH/launcher/dynatrace.sh restart

Minimum free disk space requirements were updated

To better address real-world scenarios, we've increased the required free space for new installations to the following:

There are also now separate values for new installations and upgrades. The previous, lower values are still used during upgrades for backward compatibility. The new, higher values are applied for fresh installations. Before each upgrade, we perform sanity checks for Cassandra, Elasticsearch, and transaction datastores to ensure that they have at least 1 GB of free space available.

Other improvements

Additionally, all new features introduced with Dynatrace SaaS version 1.169 and version 1.170 are now also supported by Dynatrace Managed.

Resolved issues