Troubleshootingedit

Some errors in the application appear to be originating from the agent’s JavaScript fileedit

In some cases when you look at the stack trace of an error, it appears to be originating from the agent’s JavaScript file. However, since we need to patch some browser APIs in order to provide some of the core functionalities of the agent, our JavaScript file appears in the error stack trace. Often, the error is generated from another part your application, you can follow the stack trace further to identify the offending code.

Of course, there are errors that might have been caused by the agent itself and we appreciate it if you report them back to us.

No stack trace available in the Span detail viewedit

The RUM JS agent does not support stack traces for spans due to performance concerns related to gathering stack information.

Debuggingedit

In order to debug the agent consider performing the following steps:

  1. Add logLevel: 'debug' to the agent configuration
  2. Reload the application
  3. Wait at least 5 seconds after the page has loaded
  4. Monitor the Console and Network panel in your browsers developer tools

Disable the Agentedit

In the unlikely event the agent causes disruptions to a production application, you can disable the agent while you troubleshoot.

To disable the agent, set active to false.

Get in touchedit

If you have any questions, please create a new topic in the Elastic APM discuss forum.

For bug reports and feature requests, please create an issue on our github repo and include as much information as possible. See Debugging for how to gather debugging information.