To configure OneAgent traffic or web UI traffic on a Cluster node, follow the steps for the Cluster Management Console or the Cluster REST API.
Certain deployments may require that specific nodes only serve UI traffic and not process OneAgent data. Or the opposite, where nodes only process OneAgent data and don't serve UI traffic. By configuring one or the other of these options, you can achieve higher stability, better cache behavior, and faster UI response times.
To improve DNS load-balancing performance, starting with Dynatrace Managed 1.214, web UI traffic is by default turned off when installing the thirteenth and subsequent nodes (or the seventh and subsequent nodes in a data center for Premium High Availability). You can enable or disable web UI traffic for a node via the Cluster REST API.
Use the Cluster Management Console to configure OneAgent traffic and web UI traffic for a Cluster node.
To disable OneAgent traffic (that is, to set a Cluster node to idle mode), follow these steps.
To enable OneAgent traffic on a node, repeat steps 1 through 3, then select Enable OneAgent traffic to start monitoring data processing on the node.
After the change, the node menu shows the opposite option, for example Enable OneAgent traffic after you disable the traffic.
To disable web UI traffic (that is, to set a Cluster node to idle mode), follow these steps.
To enable web UI traffic on a node, repeat steps 1 through 3, then select Enable Web UI traffic to start serving web UI traffic on the node.
After the change, the node menu shows the opposite option, for example Enable Web UI traffic after you disable the traffic.
Use the Cluster REST API to configure OneAgent or web UI traffic for a Cluster node.
You can configure this option using an API call. See POST /cluster/configuration.
To run this request, you need the Cluster token management permission assigned to your API token. If you don't have the API token, you can generate one.
Go to Access Tokens.
Select Generate token and enter a name for your token.
Select the Service Provider API permissions and select Generate.
Use the generated API token to run the API calls.
You can POST to the /api/v1.0/onpremise/cluster/configuration endpoint with the following parameters:
| Parameter | Type | Description | In | Required |
|---|---|---|---|---|
| integer | ID of the node | body | Yes |
| boolean | Whether this node serves web UI requests ( | body | Yes |
| boolean | Whether this node receives OneAgent traffic ( | body | Yes |
| string | Not in use | body | No |
An example of a JSON payload for the API call:
{"clusterNodes": [{"id": 1,"webUI": true,"agent": true,"datacenter": "dc-1"},{"id": 2,"webUI": true,"agent": true,"datacenter": "dc-1"}]}
The API responds with "lockAcquired": true when it accepts the change. To follow the change, call GET /cluster/configuration/status. The change is complete when state is SUCCESS.