The new cloud experience 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.
The underlying observability data is all powered by Grail, which supports flexible analytics through the Dynatrace Query Language in
Notebooks,
Dashboards, and
Workflows.







Clouds is automatically installed as a core app managed by Dynatrace.
See concepts for the comparison between classic and new cloud connections.
The following table describes the required permissions.
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 and the type of cloud connection (new or classic).
Use the following guide to set up and configure a new AWS cloud connection in Dynatrace.
The Overview New 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 and/or Azure services based on new cloud connections at a glance. On that page, you can:
Select the AWS services or Azure services tile, choose a specific service category, or select the counter in the upper-right corner of the tile to access the Explorer New tab with a list of selected services.
Review the health state of cloud services, depending on your alert setup. To list the unhealthy services in Explorer New, select the red counter (if any) in the upper-right corner of the tile.
Open ready-made dashboards for the most popular services (for example, AWS Lambda) or select Browse all dashboards to list all ready-made dashboards for AWS and/or Azure.

Use the Explorer New tab 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:

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 ready-made health alerts and warning signals for your cloud services, as well as alert templates for setting up additional custom alerts for popular AWS services.
Health alerts and warning signals are provided and maintained out of the box by Dynatrace.
A health alert creates a Dynatrace problem that triggers root-cause analysis in Dynatrace.
A warning is created for a resource when the observation is not critical and shouldn't raise a problem.
Health alerts and warning signals are both surfaced in
Clouds.
You can easily adopt ready-made health alerts and warning signals for your AWS accounts either upon your AWS connection onboarding or in
Settings.
If you want to create new or update ready-made health alerts and warning signals, go to
Settings > Analyze and alert > Alerts > Cloud services, where you can create, update, and enable/disable alerts for your connections.
storage:metrics:readstorage:buckets:readdavis:analyzers:executeus-east-1 to get alerts and warnings only for cloud services hosted in that region.

Dynatrace provides predefined alert templates to allow for additional custom alerts on popular cloud services. These alert templates are complementary to ready-made health alerts and warning signals.
You can easily create new custom alerts directly in
Clouds by selecting a template and New Alert.
Next, you can either customize the alert in the Anomaly Detection wizard or create the alert with one click.

You can find all custom alerts and more information around capabilities and limits in
Anomaly Detection.
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've already used Dynatrace for cloud platform monitoring, the classic connections and Explorer (Classic connections) continue to provide the same 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 (AWS, Preview for Azure)
The newest cloud platform connections by Dynatrace provide an easier, more flexible, and more powerful way to connect AWS and Azure cloud accounts with Dynatrace. Support for GCP will follow soon.
All data is natively stored in Grail and surfaced on the Overview New and Explorer New 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 on the Explorer (Classic connection) tab in
Clouds and have no specific licensing requirements.
The Explorer New and Overview New tabs 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.
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.
Problem mode enables precise investigation and analysis of any health-related issues.
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.
You have access to the following ready-made dashboards for the new AWS Cloud Platform Monitoring:
The ready-made dashboards can be accessed through:
Dashboards
Open
Dashboards, select Ready-made dashboards in the left menu, and search for aws.
Clouds
Clouds and select the Overview New tab. You can then either select one of the more 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.
Segments allow you to logically structure and conveniently filter observability data across apps on the Dynatrace platform. Segments are available within the new Explorer New 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:
aws.account.id, aws.region)Example segment definition by AWS Account ID:

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.
CloudsThe 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.
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.
You can find more information and join the Cloud Platform Monitoring for Azure Preview through our Preview program page.
CloudsInfrastructure Observability