If you are asking about a problem you are experiencing, please use the following template, as it will help us help you. If you have a different problem, please delete all of this text
Kibana version: 7.0.1
Elasticsearch version: 7.0.1
APM Server version: 7.0.1
Browser version: Version 75.0.3770.80 (Official Build) (64-bit)
Original install method (e.g. download page, yum, deb, from source, etc.) and version: https://email@example.com/dist/bundles/elastic-apm-js-base.umd.min.js
Fresh install or upgraded from other version?
Is there anything special in your setup? For example, are you using the Logstash or Kafka outputs? Are you using a load balancer in front of the APM Servers? Have you changed index pattern, generated custom templates, changed agent configuration etc.
Description of the problem including expected versus actual behavior. Please include screenshots (if relevant):
We've got RUM(JS) agent running in our Rails application and it was running fine. Recently we've had some issues with our stack due to elasticsearch storage filling up and not being able to accept new index creation. The problem that I want help with is the fact that with elasticsearch not being able to accept new events the RUM(JS) library started throwing 503s with "Failed sending transactions" and these errors were preventing the rest of the JS in the page to load properly thus breaking user experience. Shouldn't the library catch said errors to prevent it to disrupt execution context and log it only? We are currently fine tuning our storage process and as such we might run into this problem again, and we can't have the user experience being affected to it. What do you recommend?
Steps to reproduce:
- Fill up Elasticsearch disk storage
- Enable RUM agent on a page
Errors in browser console (if relevant):
Provide logs and/or server output (if relevant):