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.

See below how you can integrate OneAgent with your Azure Spring Cloud application to monitor your Spring Cloud workloads with Dynatrace.

Prerequisites

Set up integration

1. Prepare your environment in Azure

  1. In Azure Portal, create an Azure Spring Cloud instance.

  2. 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.

    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:

  • DT_TENANT
  • DT_TENANTTOKEN
  • DT_CONNECTION_POINT.

Before you begin, collect the following information:

  • Your Dynatrace environment ID
  • Authentication
    • 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.
  1. The value for DT_TENANTis your Dynatrace environment ID.

  2. To determine the values for DT_TENANTTOKEN and DT_CONNECTION_POINT, make an API request to the Deployment API - GET connectivity information for OneAgent endpoint. The values you need are returned as tenantToken and communicationEndpoints.

    You can submit the call to your environment URL (SaaS or Managed) or an Environment ActiveGate URL.

    • Dynatrace SaaS:

      curl https://<your-environment-id>.live.dynatrace.com/api/v1/deployment/installer/agent/connectioninfo?Api-Token=<your_PaaS_token>
      

      Replace:

    • Dynatrace Managed:

      curl https://<your-domain>/e/<your-environment-id>/api/v1/deployment/installer/agent/connectioninfo?Api-Token=<your_PaaS_token>
      

      Replace:

    • Environment ActiveGate:

      curl https://<your-activegate-domain>/e/<your-environment-id>/api/v1/deployment/installer/agent/connectioninfo?Api-Token=<your_PaaS_token>
      

      Replace

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>

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: AppFlow

Example CPU consumption: diagnostic-cpu

Example response time analysis: resposetime

OneAgent updates

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.