-
Notifications
You must be signed in to change notification settings - Fork 251
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
If internet goes out, Bugsnag slows down all requests 20x #628
Comments
Hi @bgold0 thanks for the report! |
We've started looking into whether we could fix the root cause of this slow down in advance of adding offline support. We haven't so far been able to reproduce the behavior you describe though. We've tried setting up a test with an Express server with 30 parallel processes sending an error to the Bugsnag API 100 times in quick succession. We haven't been able to measure any difference in the time taken even when making the end-point unresponsive causing all API requests to timeout and fail. Are you able to provide a reproduction case? |
Hey @mattdyoung, I appreciate the update and trying to take care of the issue. Anyway you can send the source of you trying to reproduce it? It would save me some time in reproducing a working version for you. |
Hi @bgold0 Attached is our attempt to reproduce. Hopefully you can spot what's different in your usage and adapt the reproduction case. Thanks! |
We have bugsnag on a server in a location where it has intermittent internet access. Our express server talks to a local database and only uses the internet to send bugsnag reports.
When there is internet, everything works as expected. However, when there is no internet and bugsnag needs to send a bug report, it intercepts all the requests and tries to send the bug report 10 times before it let's the request go through.
Essentially turning a 500ms call to a 10,000 - 15,000ms call.
Steps for Reproduction:
The text was updated successfully, but these errors were encountered: