Migrate containerized Dynatrace ActiveGate

If you deployed containerized Dynatrace ActiveGate, the easiest way to connect it to Dynatrace Managed to SaaS is reconfiguration of ActiveGate deployment.

Step 1

Generate new tokens and determine communication endpoints

Step 2

Create new Kubernetes secrets

Step 3

Update ActiveGate resource file

Step 1 Generate new tokens and determine communication endpoints

  1. Create a new authentication token for SaaS tenant
  2. Determine the ActiveGate communication endpoints and authentication for SaaS tenant. Use the GET connectivity information for ActiveGate API.

Step 2 Create new Kubernetes secrets

  1. Create a new secret that holds the authentication details to the Dynatrace SaaS server used by ActiveGate.

    kubectl -n dynatrace create secret generic dynatrace-tokens-saas \
    --from-literal=tenant-token=<YOUR_TENANT_TOKEN> \
    --from-literal=auth-token=<YOUR_AUTH_TOKEN>

    You need to replace

    • <YOUR_TENANT_TOKEN> with the tenantToken value obtained in Step 1 from the connectivity information.
    • <YOUR_AUTH_TOKEN> with the individual ActiveGate token obtained in Step 1.

Step 3 Update ActiveGate resource file

Modify your YAML in your deployment file as follows, making sure to replace all the placeholders

  1. Update the environment parameters values:

    Parameter

    Updated value

    Notes

    DT_TENANT

    {your-environment-id}

    To determine your environment ID, see the syntax below.

    SaaS: https://{your-environment-id}.live.dynatrace.com

    DT_SERVER

    {your-communication-endpoints}

    This is a comma-separated list of the communication endpoints to be used by ActiveGate to send data to your Dynatrace environment.

    To determine your communication endpoint check the value of communicationEndpoints obtained in Step 1 from the connectivity information.

  2. Rename secretName dynatrace-tokens to dynatrace-tokens-saas to use the newly created secret with authorization data.