Question: Why are the Agent IDs used for Cross Domain Session Correlation different for each enabled application?
Answer: This is not the expected behavior, as the Agent IDs should be the same for each application using Cross Domain Session Correlation.
This issue can occur when the adrum-xd.html file is hosted on different domains for each application. For Cross Domain Session Correlation to work, all pages on the multiple domains have to access the same copy of adrum-xd.html that is hosted on a single domain.
Question: Is there any way to confirm whether the JavaScript Agent is sending a cross-domain-capable beacon?
Answer: To check whether the JavaScript Agent is sending a cross-domain-capable beacon, look at the beacon “ai” field, which standards for “agent ID.” If agent ID starts with “XD_”, cross domain works on the JavaScript agent.
Question: How often is the file adrum-xd.html (which is used to enable Cross Domain Session Correlation) loaded?
Answer: The adrum-xd.html file is loaded into a hidden iframe once every 2 weeks.
Question: Is it possible to see Cross Domain Sessions across multiple AppDynamics applications?
Answer: No, it's not possible. In our Cross Domain Session Correlation, we only support sessions that are across domains but within the same AppDynamics application.
More info on Cross Domain Session Correlation: Configure the JavaScript Agent.
