This is part one of a blog post series explaining how to use security policies to set permissions within Dynatrace. In this post, you'll learn about the new permissions for environment roles, which extend the coverage of our security policies.
Dynatrace enables configuration-as-code for logs, making data acquisition, filtering, masking, and anonymizing scalable in enterprise environments. Orchestrating a fleet of OneAgents from a central configuration point removes error-prone manual work for DevOps and SRE teams across dynamic IT landscapes.
Dynatrace Davis Assistant will reach end of life on January 31, 2023. After this date, the service will be shut down, and interactions with Davis Assistant will no longer be possible. Existing integrations, for example, with Slack or Microsoft Teams, will cease to work at that time.
For options and best practices on managing the push of problem notifications to your preferred third-party incident management or ChatOps service, see problem notifications documentation.
Cross Solutions | IAM
You can now manage the classic roles-based access using Dynatrace IAM. For more information, see Migrate role-based permissions to Dynatrace IAM policies.
Infrastructure Monitoring | Log Monitoring
Dynatrace allows you to include and exclude specific log sources for analysis by Dynatrace Log Monitoring.
The storage configuration is based on rules that use matchers for hierarchy, log path, and process groups. These rules determine the upload of log files known to OneAgent, auto-detected log files, and custom log files defined per process group.
Infrastructure Monitoring | Log Monitoring
Dynatrace allows you to define rules that control log data timestamps.
Log Monitoring now provides the ability to define a specific date format using timestamp rules to specify what should be considered a timestamp in the log record.
Cross Solutions | Settings
We introduced a mechanism for remote configuration management for OneAgents and ActiveGates.
You can now perform bulk configuration at scale and control it centrally from the Dynatrace Deployment status page or by using the Dynatrace API.
The following configuration options are now available for remote configuration management:
For more information, see Remote configuration management of OneAgents and ActiveGates.
Cross Solutions | Data Explorer and dashboards
If you are upgrading Custom charts to Data Explorer charts, we have added a Custom charts: Yes
filter to the Dashboards table to make it easy for you to identify dashboards that still need to be upgraded. For details, see Upgrade your custom charts now.
Cross Solutions | Problems
You can avail of a larger email body size when configuring email templates for problem notifications—the size of the email body has been increased from 5,000 characters to 10,000 characters.
Application Security | Third-party vulnerabilities
Resolved third-party vulnerabilities can now be muted and unmuted. Muted resolved third-party vulnerabilities remain muted if they are reopened.
Infrastructure Monitoring | Kubernetes
You can now filter the Kubernetes workload list by:
Infrastructure Monitoring | Kubernetes
externalName
field. This property is only defined for Kubernetes services of type ExternalName
.Apps & Microservices | Distributed traces
When you Expand a trace from the Distributed traces list, the trace overview hosts all the related request attributes in a dedicated section.
To learn about changes to the Dynatrace API in this release, see Dynatrace API changelog version 1.252.
The 1.252 GA release contains 7 resolved issues.