Try it free

Get started with EdgeConnect

  • Latest Dynatrace
  • Getting started guide
  • 4-min read
  • Published Nov 06, 2026

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.

Who is this for?

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.

What will you learn?

Your goal is to get your first EdgeConnect online and routing requests to your internal systems.

In this tutorial, you'll learn how to:

  • Create an EdgeConnect configuration in Dynatrace.
  • Deploy EdgeConnect as a Docker container or on Kubernetes.
  • Verify that EdgeConnect shows as online in Dynatrace.

Before you begin

Prerequisites

Make sure you have:

  • A latest Dynatrace environment.
  • Required user permissions to manage EdgeConnect configurations.
  • A container runtime where EdgeConnect runs—Docker for a standalone deployment, or a Kubernetes cluster (with or without Dynatrace Operator).
  • Outbound network connectivity from the EdgeConnect host to:
    • https://sso.dynatrace.com/sso/oauth2/token
    • https://<your environment ID>.apps.dynatrace.com
  • Connectivity from EdgeConnect to your internal target systems.

EdgeConnect doesn't require any inbound connection from Dynatrace.

Prior knowledge

  • Basic experience with Docker or Kubernetes, depending on the deployment option you choose.
  • Familiarity with navigating Dynatrace settings.

Get started with EdgeConnect

Complete the following steps to get EdgeConnect up and running.

1. Configure EdgeConnect in Dynatrace

Create an EdgeConnect entry in Dynatrace settings with a name and host patterns, then download the generated edgeConnect.yaml configuration file.

  1. Go to Settings Settings > General > External Requests > EdgeConnect.

  2. Select New EdgeConnect.

    • Enter a unique name for the EdgeConnect instance. The name needs to comply with RFC 1123 label names and be at most 50 characters long.
    • Provide the host patterns of the requests EdgeConnect handles. Use a wildcard to replace the start of the host domain (for example, *.myapp.org matches staging.myapp.org and prod.myapp.org). For details about host patterns, see Host patterns.
  3. 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: Docker Deploy via Docker or Deploy via Dynatrace Operator.

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

  5. Select Download edgeConnect.yaml.

    This file is the configuration file that needs to be used for configuring the EdgeConnect image.

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

2. Deploy EdgeConnect

Choose one of the following deployment options:

  • Docker: Run EdgeConnect as a standalone Docker container with the edgeConnect.yaml file mounted in.
  • Kubernetes (manual): Deploy on Kubernetes using a Deployment manifest and Secrets, without Dynatrace Operator.
  • Kubernetes with Dynatrace Operator: Use Dynatrace Operator and an EdgeConnect custom resource to manage the deployment.
  • Operator-managed provisioning: Let Dynatrace Operator manage the EdgeConnect configuration and lifecycle. Skip step 1: Configure EdgeConnect in Dynatrace with this option. You define the host patterns in the EdgeConnect custom resource, and the Operator creates the configuration for you.

You've completed this step when the EdgeConnect container or pod is running in your network.

3. Verify the connection

After the container starts:

  1. Go to Settings Settings > General > External Requests > EdgeConnect.
  2. Check the Availability column. A connected EdgeConnect shows as online.

If it's still offline, check the container logs for error messages.

You've completed this step when EdgeConnect shows as online.

Congratulations!

You set up EdgeConnect and verified that it's online.

To explore further:

  • For multi-cluster scenarios where the same hostname appears in several environments, see Manage multiple EdgeConnect configurations.
  • To inject credentials into requests, configure secrets in edgeConnect.yaml.
  • For all configuration parameters, see EdgeConnect reference.

Related topics

  • EdgeConnect concepts
  • EdgeConnect reference
  • Test EdgeConnect routing and configure host mappings
Related tags
Infrastructure Observability