EdgeConnect lets Dynatrace apps and workflows reach your internal systems through an outbound-only container that runs in your own network. This guide shows you how to register EdgeConnect in Dynatrace, deploy the container, and verify the connection.
This guide is for platform and infrastructure administrators who manage their organization’s network and have the permissions required to manage EdgeConnect configurations in Dynatrace.
Your goal is to get your first EdgeConnect online and routing requests to your internal systems.
In this tutorial, you'll learn how to:
Make sure you have:
https://sso.dynatrace.com/sso/oauth2/tokenhttps://<your environment ID>.apps.dynatrace.comEdgeConnect doesn't require any inbound connection from Dynatrace.
Complete the following steps to get EdgeConnect up and running.
Create an EdgeConnect entry in Dynatrace settings with a name and host patterns, then download the generated edgeConnect.yaml configuration file.
Go to
Settings > General > External Requests > EdgeConnect.
Select New EdgeConnect.
*.myapp.org matches staging.myapp.org and prod.myapp.org). For details about host patterns, see Host patterns.Select Create.
Dynatrace creates the configuration and opens the Create new EdgeConnect window with the OAuth credentials and deployment commands. Select the tab that matches your deployment method:
Deploy via Docker or Deploy via Dynatrace Operator.
Copy the OAuth client ID, OAuth client secret, and OAuth client resource values and store them in a secure location.
Dynatrace displays the OAuth client secret only once. If you close the window before you copy the secret, you can't retrieve it. Otherwise, create a new EdgeConnect configuration.
Select Download edgeConnect.yaml.
This file is the configuration file that needs to be used for configuring the EdgeConnect image.
Run the commands shown in the window to deploy EdgeConnect.
EdgeConnect handles any HTTP request from your Dynatrace app functions, workflows, or ad hoc functions that matches a defined host pattern. The configuration specifies which EdgeConnect instance handles the request.
For example, given a host pattern of staging.myapp.org in its configuration, the Dynatrace runtime routes an HTTP request with the URL https://staging.myapp.org/test.html to that EdgeConnect.
Choose one of the following deployment options:
edgeConnect.yaml file mounted in.You've completed this step when the EdgeConnect container or pod is running in your network.
After the container starts:
If it's still offline, check the container logs for error messages.
You've completed this step when EdgeConnect shows as online.
You set up EdgeConnect and verified that it's online.
To explore further:
edgeConnect.yaml.