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.
Some errors in the application only show
In some cases when you look at the details of an error, the only information you can see is the message
In order to get visibility of the error’s detail, you must do two things.
Add the attribute
<script src="https://example.com/example.js" crossorigin>
Make sure that the server response includes the
// Either of the two values is valid: Access-Control-Allow-Origin: * Access-Control-Allow-Origin: your page's origin
To learn more about how browsers handle script errors, see the MDN page on the onerror event.
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.
In order to debug the agent consider performing the following steps:
logLevel: 'debug'to the agent configuration
- Reload the application
- Wait at least 5 seconds after the page has loaded
- Monitor the Console and Network panel in your browsers developer tools
Disable events payload compressionedit
In browsers such as Chrome, the RUM agent event payload is compressed with gzip. Because of this compression, you will not see readable content when inspecting the event with the Network panel of your browser developer tools.
There are situations where that can be an issue. For instance, HAR files will not show readable information. Therefore, inspecting events for debugging purposes will not be possible.
There are two ways to disable the payload compression:
Create an item named
_elastic_inspect_beacon_using the sessionStorage browser API.
Load the webpage with the query param
_elastic_inspect_beacon_in the URL. For example,
The effect of this will remain until the tab or browser is closed.
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
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.
Intro to Kibana
ELK for Logs & Metrics