Try it free

EdgeConnect

  • Latest Dynatrace
  • Explanation
  • 2-min read

EdgeConnect securely connects Dynatrace apps and workflows to internal systems by routing requests to configured hosts.

Overview

You can run EdgeConnect as a container in your network and configure it to handle requests to specific host patterns. When an app function, ad hoc function, or workflow action targets a host that matches a configured host pattern, the Dynatrace runtime forwards the request to EdgeConnect. EdgeConnect sends the request to the internal target and returns the response.

  • Host patterns and mappings: Host patterns define how requests are routed to internal hosts. Patterns are unique per configuration, and the most specific match takes precedence. Host mappings let configurations share an internal hostname, such as localhost or a Kubernetes API endpoint.
  • Scaling and security: Deploy multiple instances per configuration to spread load. EdgeConnect follows a least-privilege model that needs no inbound access, and you can restrict the hosts it can reach.

For diagrams and examples, see EdgeConnect concepts.

Get started

Progressive delivery

EdgeConnect initial setup

Follow these steps to configure, deploy, and verify EdgeConnect in your system.

Concepts

How EdgeConnect works

Securely connect Dynatrace services to private networks.

Host patterns and mappings

How requests route to configurations.

Security model

Least-privilege model and best practices.

How to

Deploy on Docker

Run as a Docker container.

Deploy on Kubernetes

Run on Kubernetes without Operator.

Set up via Operator

Run on Kubernetes via Dynatrace Operator.

Automate lifecycle with Operator

Operator-managed lifecycle automation.

Configure certificates and secrets

Add custom TLS certificates and inject secrets.

Use cases

Test routing and configure host mappings

Verify which configuration handles a URL, and set up host mappings.

Manage multi-cluster deployments

Run more than one EdgeConnect configuration in the same environment.

References

User permissions

EdgeConnect permissions, configuration fields, requirements, and limits.

Operator parameters

Custom resource parameters.

Requirements and limits

Resource needs and traffic limits.

Related tags
Infrastructure Observability