Try it free

Cluster node ports

  • Reference
  • 3-min read

Configure your firewall to open the following Dynatrace Managed ports for bi-directional communication, including between all Cluster nodes in a typical Managed deployment.

Ports used by Dynatrace Managed

PortUsed byNotes

443

UI, OneAgent, and REST API

Routed to local port 8022 via an iptables prerouting rule; must remain open to allow incoming traffic from your data center; all Managed Cluster communication uses HTTPS with strong encryption

5701-5710

Hazelcast In-memory data grid platform

Distributes data evenly across Cluster nodes and enables horizontal scaling; required only for communication within the Managed Cluster; ports can be blocked for traffic from outside the Managed Cluster

5711, 8018

Nodekeeper

Required only for communication within the Managed Cluster; ports can be blocked for traffic from outside the Managed Cluster

7000, 7001, 9042

Cassandra-based Hypercube storage

Required only for communication within the Managed Cluster; ports can be blocked for traffic from outside the Managed Cluster

7199

Cassandra JMX

Required only for communication within the Managed Cluster; port can be blocked for traffic from outside the Managed Cluster

8019

Upgrade UI

Required only for communication within the Managed Cluster; port can be blocked for traffic from outside the Managed Cluster

8020

Dynatrace Server (HTTP)

Required only for communication within the Managed Cluster; port can be blocked for traffic from outside the Managed Cluster

8021

Dynatrace Server (HTTPS)

Required only for communication within the Managed Cluster; port can be blocked for traffic from outside the Managed Cluster

8022

NGINX (HTTPS), target of the port 443 routing rule

Can be used in place of port 443 when a non-privileged port is required; ports can be blocked for traffic from outside the Managed Cluster

84431

Monitoring data from OneAgent, nodes within the Managed Cluster

OneAgent sends data outbound to the Managed Cluster only, so no listening port is opened on the monitored host; each host with OneAgent must have access to this port, which must also remain open for inter-node communication

9200, 9300

Elasticsearch-based search engine

Required only for communication within the Managed Cluster; ports can be blocked for traffic from outside the Managed Cluster

9998

Embedded ActiveGate

For communication within the Managed Cluster only

1

Environments running a Managed Cluster version earlier than 1.166 use port 8443. New environments still use port 8443, but it does not need to be exposed outside the Cluster nodes. Upgraded environments preserve the port settings from the previous version.

Outbound communication to Mission Control

All Cluster nodes must be able to communicate with Mission Control to receive software updates and exchange data. Allow outbound traffic to the following IPv4 addresses:

  • 13.228.109.33
  • 46.137.81.205
  • 52.5.224.56
  • 52.48.91.146
  • 52.200.165.10
  • 52.221.165.63

Domains used:

  • mcsvc.dynatrace.com
  • mcsvc-us.dynatrace.com
  • mcsvc-eu.dynatrace.com
  • mcsvc-ap.dynatrace.com

All Managed Cluster data that Mission Control receives through these domains is hosted in the U.S. regions.

To support compliance with United States export restrictions2, if you plan to host a Managed Cluster or monitor Huawei Cloud services (or any Huawei affiliate), contact Dynatrace Support to configure a Europe or Asia/Pacific endpoint.

2

The Dynatrace Software may not be exported or re-exported from the U.S. to (a) any Group E country listed in SUPPLEMENT NO. 1 TO PART 740–COUNTRY GROUPS (Currently Syria, North Korea, Iran, and Cuba) or the Crimea Region of Ukraine, or (b) any company, entity, or person listed as a party of concern found in the list of parties of concern (currently including Huawei Technologies and its affiliates worldwide), or (3) for any end-use related to the development, production, or use of nuclear, chemical, or biological weapons or missiles. Contracts between Dynatrace and its customers require compliance with these and other export control laws.

Mission Control communication uses HTTPS and WSS over port 443 with TLS v1.2. The TLS/SSL certificate is provided by Amazon and renewed automatically each year.

Mission Control communication can be routed through a proxy. The proxy must support WebSockets and the SNI TLS extension.