Try it free

Test EdgeConnect routing and configure host mappings

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

After your EdgeConnect is online, you can verify how the Dynatrace runtime routes traffic to it and rewrite request hosts when multiple configurations need to reach services on the same internal hostname.

Prerequisites

If you haven't deployed your first EdgeConnect yet, start at Get started with EdgeConnect.

Test your configurations

To test which EdgeConnect configuration handles a URL in your environment:

  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. The request runs through the Dynatrace runtime so you can verify the EdgeConnect connection.

For background on host patterns and how the runtime selects the most specific match, see Host patterns.

Configure host mappings

Host mappings rewrite the host of matching requests to a different target hostname before EdgeConnect forwards them. Use them when multiple EdgeConnect configurations need to reach internal services that share the same hostname (for example, services on localhost or the Kubernetes API across multiple clusters).

To configure host mappings:

  1. Go to Settings Settings > General > External Requests > EdgeConnect.
  2. Select the configuration you want to edit.
  3. In the settings panel for the selected configuration, expand Host mappings.
  4. Define one or more rules using the From and To fields. EdgeConnect rewrites any request whose host matches one of the hosts in From to the host in To.

Isolate multiple services on localhost

When several services listen on localhost, give each one a unique host pattern and map it back to localhost. Each request then routes to the correct configuration but reaches the container as a standard localhost call.

For example:

  • Configuration service-a defines the host pattern localhost-service-a and maps it to localhost.
    • A request to http://localhost-service-a/myservice is routed to configuration service-a. Before the request reaches the EdgeConnect container, EdgeConnect rewrites the target to http://localhost/myservice.
  • A second configuration service-b independently defines the host pattern localhost-service-b and maps it to localhost.
    • A request to http://localhost-service-b/otherservice routes to service-b (a separate EdgeConnect deployment) and reaches it as http://localhost/otherservice.

Reach the same Kubernetes API across multiple clusters

Every cluster exposes its Kubernetes API at the same internal address, kubernetes.default.svc.cluster.local. Give each cluster a unique host pattern and map it back to that shared address, so requests reach the right cluster while the container receives a standard in-cluster call.

For example:

  • EdgeConnect configuration k8-api-dev defines the host pattern kubernetes-api-dev-cluster and maps it to kubernetes.default.svc.cluster.local.
  • A request to https://kubernetes-api-dev-cluster/api/v1/pods is routed to the EdgeConnect deployment in the dev cluster and rewritten to https://kubernetes.default.svc.cluster.local/api/v1/pods.
  • A second configuration k8-api-production defines the host pattern kubernetes-api-production-cluster, with the same target host mapping, deployed in the production cluster.
  • Requests sent to https://kubernetes-api-dev-cluster/api/v1/pods and https://kubernetes-api-production-cluster/api/v1/pods are routed to their respective clusters.

These distinct patterns let you manage each cluster independently.

For a detailed walkthrough of this pattern, see Set up EdgeConnect for the Kubernetes Connector manually.

Next steps

  • For multi-cluster scenarios where the same hostname appears in several environments, see Manage multiple EdgeConnect configurations.
  • 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