Network Requirements
Deploying the Controller often calls for configuration changes to existing network components, such as firewalls or load balancers in the network. If the Controller will reside behind a load balancer or reverse proxy, you need to set up traffic forwarding for the Controller. You may also need to Ports Settings on firewalls or any other device through which traffic must traverse.
The following are general considerations for the environment in which you deploy Splunk AppDynamics On-Premises. See Platform Installation Quick Start for other network configuration requirements.
Correlation HTTP Header
Splunk AppDynamics adds a custom header to traffic in the monitored environment named singularityheader. This header enables Splunk AppDynamics to correlate traffic across tiers. It's important to ensure that any load balancer, proxy, or firewall in the network between monitored tiers or between the tiers and the Controller preserves the header added by Splunk AppDynamics.
Clock Management
To ensure consistent event time reporting across the Splunk AppDynamics deployment, App Agents attempt to synchronize their time with the Controller time.
They do so by retrieving the time from the Controller every five minutes. App Agents then compare the Controller's time to its own local machine's clock time. If the times are different, whether ahead or behind, it applies a time skew based on the difference to the timestamps for the metrics it reports to the Controller.
If, despite the agent's attempt to report metrics based on the Controller time, the Controller receives metrics that are time-stamped ahead of its own time, the Controller rejects the metrics. To avoid this possibility, we recommend maintaining clock-time consistency throughout your monitored environment.