Customize IP address detection for custom applications
When web requests and RUM beacons are directly sent to an instrumented server, Dynatrace identifies the IP addresses of your end users' devices via the socket connections.
When you use uninstrumented components such as load balancers, CDNs, or proxies, the remote IP address is different from the original IP address. For such cases, Dynatrace also watches certain HTTP headers. These headers are most frequently used to identify the originating IP address when a client connects to a web server through an HTTP proxy, a CDN, or a load balancer.
You can view the list of headers that Dynatrace uses to determine client IP addresses for your applications. To do that, go to Settings > Web and mobile monitoring > IP determination. Dynatrace processes these headers in a specific order, but you can change the processing order and add your own headers.
Manage default headers
You can update header names, delete headers you don't need, and change the order in which Dynatrace processes the headers.
- Go to Settings > Web and mobile monitoring > IP determination.
- Manage the headers:
- To rename a header, select Expand row
, and then enter a new header name. - To delete a header, select Delete row
. - To change a header's priority, select and hold Drag row
next to the header name, and move the header up or down.
- To rename a header, select Expand row
Add your custom client IP headers
If your client IP addresses are located in a different header, create a custom rule so that Dynatrace can correctly identify the IP addresses.
To add a custom client IP header
- Go to Settings > Web and mobile monitoring > IP determination.
- Select Create custom client IP header.
Provide the name of your header.
You can create up to 10 custom client IP headers per environment.
Adding a custom client IP header might be required in one of the following cases.
- When the header that contains your client IP addresses is not in our list of headers under Settings > Web and mobile monitoring > IP determination.
When the client IP addresses for your applications are stored in a proprietary header.
When the client IP addresses are not detected correctly, for instance, when the IP addresses of your load balancers are shown in Dynatrace.
Reasons for incorrect client IP addresses
There might be several reasons why you don't see the correct client IP addresses for your application. Check the sections above for detailed instructions.
| Issue | Possible solution |
|---|---|
| The client IP addresses for your applications are located in a header that is not in our list. | Add a custom client IP header. |
| You have provided the incorrect custom client IP header. | Update the header name. |
| The custom client IP header that you provided does not actually contain IP addresses. | Specify another custom client IP header. |
| The order of the headers is not correct. | Change the processing order of the headers. |
| Your infrastructure isn't configured to add a header that propagates the client IP addresses. | Reconfigure your infrastructure. |
| The header that contains the client IP addresses is not part of the beacon requests.1 | Reconfigure your infrastructure. |
1 The IP detection headers in regular requests of the application are irrelevant for the IP detection of captured RUM data, even when they are captured as traces and those traces are correlated to user actions. |