The new Cloud Platform Monitoring (new cloud connections and the upgraded Clouds app) is available for AWS in Preview program.
Azure and Google Cloud will follow.
This new monitoring experience is currently part of our preview program and is governed by our preview terms. The data model, apps, and functionalities offered within the preview are not complete and may be significantly changed until the general availability.
The new Cloud Platform Monitoring is optimized for Cloud (Platform) Operation teams and Site Reliability Engineers (SREs) and focuses on health, troubleshooting, and performance optimization use cases of (multi-)cloud environments. The centerpiece of this experience is Clouds.
Clouds is automatically installed as a core app managed by Dynatrace.
DPS license is required with the following capabilities:
The following table describes the required permissions.
Permission
Description
settings:objects:write
1. Modify the outbound connections allowlist - might be required by Integration manager if Config v1 API domain has not been already allowed. 2. Write permissions to settings of ownership (settings:schemaIds = builtin:ownership.teams) - not strictly required. Enables additional features in Ownership tab in entity details panel.
settings:objects:read
1. Read the outbound connections allowlist - required by Integration manager. 2. Read settings of ownership (settings:schemaIds = builtin:ownership.config) - required by Ownership tab in entity details panel.
state:user-app-states:read
Read user app state. Necessary for presenting events in Events tab in entity details panel. Required by Integration Manager (connections).
state:user-app-states:write
Storing per-user app state. Required by Integration Manager (connections).
storage:buckets:read
Base permission to read records from Grail buckets. Required additionally to a table permission.
storage:entities:read
Read records from entities table.
storage:logs:read
Read records from logs table. Necessary for presenting logs in entity details panel.
storage:metrics:read
Read timeseries from the metrics table. Necessary for presenting metrics in services table and in entity details panel.
storage:events:read
Read records from the events table. Necessary for presenting problems in services table and in entity details panel.
storage:fieldsets:read
Read masked/sensitive fields
10
1
1 of 9
Clouds has an integrated onboarding flow that guides you through all the required steps to get started. The exact steps you need to take depend on your cloud provider.
AWS (Preview)
If you don’t have any existing cloud connection, go to the Overview tab or use the header bar in Clouds and select Create connection > AWS (Preview).
If you want to upgrade an existing classic connection to the new cloud platform monitoring, delete the classic connection first and then create a new cloud connection for the respective AWS Account.
Azure and GCP (Classic connections)
At this stage of the preview, the new cloud connections are not yet available for Azure and GCP. For them, you can create only classic connections.
In Clouds, use the header bar (or the Overview tab if you don’t have any existing cloud connections) and select Create connection > Azure (Classic connections) or Create connection > GCP (Classic connections).
The Overview tab is the landing page, where you can start discovering Clouds, get data into Dynatrace, and see a summary of the health state of your AWS services based on new cloud connections at a glance. On that page, you can:
Select the AWS services tile, choose a specific service category, or select the counter in the upper-right corner of the tile to access the Explorer (Preview) tab with a list of selected AWS services.
Dynatrace determines the health state of cloud services depending on your alert setup. To list the unhealthy services in Explorer (Preview), select the red counter (if any) in the upper-right corner of the tile.
Open ready-made dashboards for the most popular AWS services (for example, AWS Lambda) or select Browse all dashboards to list all ready-made dashboards for AWS.
The new Explorer (Preview) tab allows you to analyze your AWS cloud services and environments. You can explore, filter, and analyze data using various features in Clouds.
In the sidebar on the left, you can select a specific service category (such as Containers or Functions) or analyze all services. In addition, you can quickly filter by predefined attributes that are relevant for the selected category. Select any attribute in the facets sidebar and select Update to get results. The filter field is updated with your selection.
Alternatively, select the filter field at the top to view suggestions and enter filtering options. Add more statements to narrow down the results. Criteria of the same type are grouped by OR logic. Criteria of different types are grouped by AND logic. You can filter services using tags, alert status, and attributes like name or region. This helps you focus on specific subsets of services based on your criteria. For more details on the filter field syntax, see Filter field.
You can explore data in the table using the available perspectives:
Health
Utilization (for compute services)
Metadata
To tailor the results details that you see in the table, select Column settings and select the columns you want to display.
Select a specific cloud service in the table to analyze all data in context: metrics, logs, events, metadata, configuration, and topology. Select Go to dashboard to navigate to the respective ready-made dashboard while maintaining the selected timeframe and filters.
Clouds provides pre-defined alert templates for the most popular AWS services. You can easily create a new Davis anomaly detector (custom alert) by selecting a template and New Alert. Next, you can either customize the alert in the Davis Anomaly Detection wizard or create the alert with one click.
You can find all custom alerts and more information around capabilities and limits in Davis Anomaly Detection.
For this preview, all alert templates have a common suffix (Preview) in the Event title. We strongly recommend keeping this name as is to find and remove alerts created during the preview phase. In the future, Dynatrace will provide ready-made health alerts on top of custom alert templates.
The Explorer (Classic connections) tab surfaces data coming from classic cloud connections and allows for the analysis of cloud services across AWS, Azure, and GCP. If you have already used Dynatrace for cloud platform monitoring, the classic connections and Explorer (Classic connections) continue to provide the same level of value.
Clouds provides a comprehensive view of your (multi-)cloud environments, enabling you to optimize the health, performance, and resource utilization of your cloud services.
Currently, Clouds supports two types of cloud connections:
New cloud connections (Preview for AWS)
The newest cloud platform connections by Dynatrace provide an easier, more flexible, and more powerful way to connect AWS with Dynatrace.
All data is natively stored in Grail and surfaced in the new Overview (Preview) and Explorer (Preview) tabs within Clouds.
Classic connections
The classic cloud connections are available for AWS, Azure, and GCP within the previous (AWS Classic, Azure Classic, GCP Classic) and latest Dynatrace.
Classic connections are surfaced within the Explorer (Classic connection) tab in Clouds and have no specific licensing requirements.
The new Explorer view and the new Overview page only operate upon data originating from new AWS cloud connections. Azure and GCP will follow in the future.
Each perspective on monitoring your cloud services can be tailored to your needs by showing or hiding columns in the table.
Health—provides health-related information
Utilization (available for compute services)—provides perspective focuses on operational efficiency
Metadata—surfaces additional information, such as cloud tags
Health and Custom Alerts (Preview)
In the Health perspective, you can see each cloud service's health and custom alerts. When you hover over a health or custom alert badge, you see the problems and further analysis options.
Select View event to directly navigate to the details, such as relevant metrics for the respective problem.
Select Investigate problem to enter the Problem mode.
Problem mode enables precise investigation and analysis of any health-related issues.
This mode highlights the most relevant metrics associated with the alert and narrows down the timeframe to the start and end times of the selected problem.
Additionally, it offers quick access to the underlying problem, allowing you to efficiently diagnose and resolve issues.
You can use Davis CoPilot to get additional insights about the problem and potential remediation steps.
Problem mode is always active when you navigate from a specific problem in Problems to Clouds.
Clouds operates in Problem mode whenever a problem is highlighted next to the filter bar at the top of the app.
Along with the Clouds preview release, you have access to the following ready-made dashboards for the new AWS cloud platform monitoring:
AWS Foundation Networking (NAT Gateway, PrivateLink)
AWS Health Events
AWS Lambda
AWS RDS (including Aurora)
AWS S3
AWS SNS
AWS SQS
The existing AWS overview dashboard is still based on classic connections (as is). A new version based on the newest AWS cloud connections will be available soon.
The ready-made dashboards can be accessed through:
Open Clouds and select the Overview tab. You can then either select one of the most popular dashboards directly (for example, AWS Lambda) or select Browse all dashboards.
Clouds allows you to navigate from a specific service to the respective dashboard in context ( Go to dashboard). The selected timeframe, segment, and applied filters will be carried over from Clouds to the dashboard.
Filtering by (primary) tags is not yet supported out-of-the-box for the new ready-made dashboards in the AWS preview. This is already planned for a future release.
Segments allow you to logically structure and conveniently filter observability data across apps on the Dynatrace platform. Segments are available within the new Explorer (Preview) tab and can be defined easily for new cloud connections, since all data (including Smartscape nodes) is stored in Grail.
For a step-by-step guide on how to define segments for Smartscape nodes, see Filter Smartscape nodes with segments. You can use any primary Grail field (and, in the future, also tags) to conveniently define simple segments across All data:
In Clouds (or any other app that supports segments), you can then choose the segment AWS account and select one or more awsAccountIDs for filtering.
Understand your (multi-)cloud architectures and dependencies
Assess health of your cloud services
How to troubleshoot problems in Clouds
Analyze performance and resource utilization
Frequently asked questions
What if I already have existing cloud connections?
The existing, classic cloud connections stay as they are and are not automatically upgraded or removed.
To benefit from the new AWS Cloud Platform Monitoring, you need to create a new cloud connection for your AWS accounts.
The same AWS Account for the classic and new cloud connections
We do not recommend setting up the classic and new cloud connections for the same AWS account. For a heterogeneous set of AWS accounts, classic and new cloud connections can co-exist.
Clouds app) is available for AWS in Preview program.
Go to dashboard to navigate to the respective ready-made dashboard while maintaining the selected timeframe and filters.
Davis Anomaly Detection.
