Migrate from Azure classic (formerly "built-in") services to cloud services
From the Azure overview page, you can access Dynatrace classic services and cloud services for Azure monitoring. Both types of services share the same Azure 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 Azure 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 and dimensions 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 and dimensions.
If you're using classic services, we recommend migrating to cloud services to take advantage of the wider range of customizable configuration options.
Impact of the migration
Even though classic and cloud services monitor the same Azure resources on Dynatrace side, they are monitored as two different entities.
-
They have different entity IDs and metric keys.
-
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 do have the option to choose from a classic or cloud service to preserve historical data, for now. 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 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.
-
Logs from Azure log forwarder are still linked to historical data and entities.
To monitor cloud services, you need to have Environment ActiveGate configured.
Changes in the UI
Your Azure overview page changes after configuring a new version of a service.
For example, let’s look at Azure Storage Account.
- If the legacy Azure Storage Accounts service is configured, this is what the Storage accounts section of the Azure overview looks like.
- Select Cloud services to find new overview pages for the services.
- After configuring Azure Storage Account, Azure Storage Blob, Azure Storage File, Azure Storage Queue, and Azure Storage Table services, this is what the Storage accounts section of the Azure overview looks like.
Additionally, you can configure metrics for cloud services via UI.
