How the Site Extension for OneAgent works

The extension doesn't include the OneAgent installer. Instead, the extension uses the Dynatrace REST-API to download the latest installer from the cluster, unless an OneAgent default version is configured.

How to retrieve your environment ID and API Token

Environment ID

Click Copy to copy the ID to the clipboard. You can do this at any time by revisiting this page.

API Token

The API token is used in combination with your environment ID to download OneAgent. Go to Deploy Dynatrace > Set up PaaS integration to access the InstallerDownload token. For security reasons, it's recommended that you create a discrete token for each environment.

To generate a new token

Click the Generate new token button.

Type in a meaningful name for your token. A meaningful token name might be the name of the platform you want to monitor (for example, azure, cloud-foundry, or openshift). To view and manage your existing tokens, go to Settings -> Integration -> Platform as a Service.

Click Generate to create the token. The newly created token will appear in the list below.

Click Copy to copy the generated token to the clipboard. You can do this at any time by revisiting this page and clicking Show token next to the relevant PaaS token.

Additional configuration parameters

Server URL
If you're using Dynatrace Managed or your cluster traffic is routed through an ActiveGate, you need to configure the communication endpoint used by the extension.

<YourDynatraceServerURL> and <YourEnvironmentID> need to be replaced. The URL pattern for the API endpoint is as follows:
https://<YourDynatraceServerURL>/e/<YourEnvironmentID>/api