Integrate OneAgent with Azure Spring Cloud
You can configure Dynatrace to fully monitor your Azure Spring Cloud workloads. Not only can Dynatrace ingest Azure Spring Cloud metrics from Azure Monitor, but it can also inject OneAgent into your application to inspect the topology and performance of each individual component.
- Full-stack monitoring powered by OneAgent
- Integration with Azure Monitor
- Automatic service detection of services running in Azure Spring Cloud
Since Azure Spring Cloud is a fully managed hosting platform, applications are deployed into a sandboxed environment that doesn't allow direct access to the underlying operating system. This results in some restrictions for OneAgent:
- Code-module support limited to Java.
- The functionality is currently available only for services (web applications, API applications, and mobile apps) on Windows.
See below how you can integrate OneAgent with your Azure Spring Cloud application to monitor your Spring Cloud workloads with Dynatrace.
Set up integration
1. Prepare your environment in Azure
In Azure Portal, create an Azure Spring Cloud instance.
In the new Azure Spring Cloud instance, create an application that you want to report to Dynatrace by running the command below.
Note: Be sure to replace the placeholders (
<...>) with your own values.sh
az spring-cloud app create --name <your-application-name> --is-public true -s <your-resource-name> -g <your-resource-group-name>
2. Determine the values for the required environment variables
To set up OneAgent integration with your Azure Spring Cloud instance, you need to configure three environment variables:
Before you begin, collect the following information:
- Your Dynatrace environment ID
- PaaS token authenticates you as a Dynatrace user and is required to determine the tenant token.
- Tenant token allows OneAgent to report data to Dynatrace. For more information on tokens, see Access tokens.
The value for
DT_TENANTis your Dynatrace environment ID.
To determine the values for
DT_CONNECTION_POINT, make an API request to the Deployment API - GET connectivity information for OneAgent endpoint. The values you need are returned as
You can submit the call to your environment URL (SaaS or Managed) or an Environment ActiveGate URL.
3. Add the environment variables to your application
Once you have the values for the environment variables required for OneAgent integration, you can add the respective key/value pairs to your application either on Azure Portal, or in the Azure CLI. See the instructions below for each of these options.
Run the command below, making sure to replace the placeholders (
<...>) with your own values determined in the previous steps.
az spring-cloud app deploy --name <your-application-name> --jar-path app.jar \ -s <your-resource-name> -g <your-resource-group-name> --env DT_TENANT=<your-environment-ID> \ DT_TENANTTOKEN=<your-tenant-token> DT_CONNECTION_POINT=<your-communication-endpoint>
Go to your Azure Spring Cloud instance and select the resource group where Dynatrace will be deployed.
Select the application for which you want Dynatrace to report data.
Select Configuration and enter the following environment variables key/value pairs.
Your Dynatrace environment ID
Your tenant token. See Determine the values for the required environment variables for details.
Your communication endpoint. See Determine the values for the required environment variables for details.
Optionally, you can customize the built-in rules for process group detection by setting another environment variable,
DT_CLUSTER_ID. The value can be the name of the process group you want to see in Dynatrace. See Customize the structure of process groups for details.
View data in Dynatrace
Once you add the environment variables to your application, Dynatrace starts collecting data from it. To view data for your Azure Spring Cloud application, in the Dynatrace menu, go to Services and select your application.
Example service flow:
Example CPU consumption:
Example response time analysis:
OneAgent updates are performed automatically with the JDK.
Following a OneAgent update, you need to restart or redeploy your applications for them to be monitored with a new OneAgent version. This is because some components of OneAgent keep running in processes that are monitored by Dynatrace.
- Before restart, these processes will continue to be monitored with the previous version of OneAgent.
- After restart, these processes will be monitored with the latest version of OneAgent.