You can create multiple EdgeConnect configurations in your environment, each with its own different host pattern configuration as explained in Configure EdgeConnect in Dynatrace.
You can run multiple EdgeConnect configurations in one environment, and deploy multiple instances per configuration. Common reasons:
staging and prod) its own configuration and host patterns.localhost or the Kubernetes API) using host mappings. See Configure host mappings.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:
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).
To change the host patterns or host mappings of an existing configuration:
Editing a configuration requires the app-engine:edge-connects:write permission. For the full permission list, see User permissions.
To remove a configuration:
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.
edgeConnect.yaml parameters and environment variables, see EdgeConnect reference.