Migrate from AWS classic (formerly "built-in") services to cloud services
From the AWS overview page, you can access Dynatrace classic services and cloud services for AWS monitoring. Both types of services share the same AWS resources. However, classic services use a predefined set of metrics, so configuring which metrics to monitor, or determining which ones are already monitored, is not supported.
Classic services vs cloud services
As previously mentioned, classic services and cloud services share the same AWS resources. However, cloud services support a wider range of configuration options, such as new metrics and customizable monitored metrics. To give you more customization options, we’ve started the following:
-
Adding more services to the Cloud services section so you can customize which metrics you want to monitor.
-
Adding more metrics for cloud services; not only are they configurable, but you can now monitor much more than before.
-
Replacing the classic services with cloud services that have more configuration options regarding metrics.
If you're using classic services, we recommend migrating to cloud services to take advantage of the wider range of customizable configuration options.
If you're using OneAgent integration for your Lambdas, we recommend Lambda migration. Since the release of Dynatrace version 1.283, we show data for the new Lambda service together with OneAgent data on the Lambda service page.
Impact of the migration
Even though classic and cloud services monitor the same AWS resources on Dynatrace side, they are monitored as two different entities.
-
They have different entity IDs and metric keys.
-
Due to their different implementations, they may detect different numbers of instances. Cloud services show only instances with metrics.
-
Data for each Dynatrace entity type is collected and stored separately.
-
Breaking change You need to adapt the configuration of dashboards, alerts, and management zones based on entity ID or metric keys with the monitored service type.
You currently have the option to choose from a classic or cloud service to preserve historical data, but be aware of the following:
-
Historical data is persisted on the classic services. If you switch back, monitored data will present gaps for the period in which the resources were monitored via the cloud service.
-
You can’t have both of them turned on simultaneously. Even though on the Dynatrace side they’re two different services, the legacy and new versions monitor the same AWS resource. If you had two versions switched on simultaneously, you would be charged double for polling the same data twice.
-
If you turn on the new version, the classic version is turned off automatically, and vice versa.
-
There is no direct link between
Entities containing historical and new data.
- Cloud service data and data coming from OneAgent for opaque Amazon RDS—not linked to the new cloud service page with CloudWatch metrics.
-
Logs from AWS log forwarder to Amazon RDS are still being linked to the historical data and entity
RELATIONAL_DATABASE_SERVICE. -
Events or problems that would have been auto-detected on the historical (classic) data might not be automatically raised. Alerting rules are not provided for these cloud services:
- Amazon RDS
- Amazon EBS
- AWS Lambda—predefined metric event configuration is provided but needs to be manually enabled.
To monitor cloud services, you need to have Environment ActiveGate configured.
Changes in the UI
Your AWS overview page changes after configuring a new version of a service.
For example, let’s have a look at Amazon EBS.
-
If the legacy Amazon EBS (classic) service is configured, this is what the EBS volumes section of the AWS overview looks like.
-
If the Amazon EBS cloud service is configured, this is what the EBS volumes section of the AWS overview looks like.
-
Select Cloud services to find new overview pages for the services.
-
Additionally, you can configure metrics for cloud services via the web UI.
