Troubleshooting JavaAgent Browser Agent
Article ID: 421759
Updated On:
Products
Issue/Introduction
The following is a high-list of techniques and suggestions to employ when troubleshooting BrowserAgent performance, display and configuration issues
Environment
DX O2
Resolution
1. Ensure BrowserAgent extension is part of the Agent package
2.To confirm BA extension is working as expected and traces listed in the Autoprobe.log, we should entries like below :
3.Access your web app, right click, select source code, you should see the snippet injected, below an example:
4. Open Developer Tools, access to your app, you should see metrics and traces collection as below
5.From AXA app you can adjust default values of axa data to collect
for example, set Metric Frequency (ms) = 0 and Enable Browser Logging
6. Review the Agent log for possible issues:
A common issue is the need to increase the max search length, search for:
[WARN] Stop injection snippet code because one of more pages exceeded max searching length 32758
Example from an Agent log:
7. To further debug the issue, enable TRACE for the Agent as below:
Do not chnage
introscope.agent.log.level.IntroscopeAgent.BrowserAgent=TRACE
Perform some activity in your web app and you should see TRACE information from BrowserAgent as below, this will help you troubleshoot issues with the snippet injection for example:
8.Ensure javascript injection is not disabled at the browser level
Additional Information
Feedback
