Try it free

Manage multiple EdgeConnect configurations and instances

  • Latest Dynatrace
  • How-to guide
  • 7-min read
  • Published Oct 01, 2026

You can create multiple EdgeConnect configurations in your environment, each with its own different host pattern configuration as explained in Configure EdgeConnect in Dynatrace.

Use multiple configurations and instances

You can run multiple EdgeConnect configurations in one environment, and deploy multiple instances per configuration. Common reasons:

  • Separate networks: Give each isolated network or environment (for example, staging and prod) its own configuration and host patterns.
  • Scale throughput: A single container processes up to 20 concurrent requests. Deploy more instances of a configuration to handle more traffic. To learn more about EdgeConnect request and response limits, see Limits.
  • Shared hostnames: Reach services that share a hostname (for example, localhost or the Kubernetes API) using host mappings. See Configure host mappings.

Host pattern rules

When using multiple configurations, host patterns can overlap across configurations. Define host patterns carefully to avoid conflicts. When patterns overlap, the runtime routes requests to the configuration with the most specific match. For more details, see Host patterns.

To test in advance which EdgeConnect would handle a given URL:

  1. Go to Settings Settings > General > External Requests > EdgeConnect.
  2. Select URL verification.
    • On the Find matching EdgeConnects tab, enter your URL and select Match.
    • On the Test HTTP request tab, enter an HTTP request and select Run test to verify the connection end-to-end.

Scale a configuration with multiple instances

To increase throughput for a configuration, deploy additional container instances that use the same edgeConnect.yaml file. All instances of a configuration connect to your environment independently, and the Dynatrace runtime distributes matching requests across the instances that have free capacity.

You don't need to change the Dynatrace settings to add or remove instances—scale the number of containers in your deployment (for example, by increasing the replica count in Kubernetes).

Edit a configuration

To change the host patterns or host mappings of an existing configuration:

  1. Go to Settings Settings > General > External Requests > EdgeConnect.
  2. Pick the configuration you want to edit, and select > Edit details.
  3. Update the host patterns or host mappings, and select Save.

Editing a configuration requires the app-engine:edge-connects:write permission. For the full permission list, see User permissions.

Delete a configuration

To remove a configuration:

  1. Go to Settings Settings > General > External Requests > EdgeConnect.
  2. Pick the configuration you want to delete, and select > Delete.

Deleting a configuration also removes its OAuth client and requires the app-engine:edge-connects:delete and oauth2:clients:manage permissions. For permission details, see User permissions.

Next steps

  • To verify which configuration handles a URL and set up host mappings, see Test EdgeConnect routing and configure host mappings.
  • For all edgeConnect.yaml parameters and environment variables, see EdgeConnect reference.

Related topics

  • EdgeConnect concepts
  • EdgeConnect reference
  • Get started with EdgeConnect
Related tags
Infrastructure Observability