You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have added a task to our backlog to allow users to override the Symfony delivery system, which would give you the ability to report errors to BugSnag asynchronously. We can't currently give an ETA on when this could be looked at, but we will make sure to update this thread with any future developments around this.
It is worth noting that we do delivery in the kernel.terminate event, so the request happens after the response has been sent to the user. This means that, although you may notice 80% of the time in your 404s is spent sending data to BugSnag, this will not be affecting the user experience.
Description
While taking a look at my Datadog's longest traces, I noticed that, for a 404, 80% of the time is spent in curl sending data to Bugsnag:
Describe the solution you'd like
My proposal is to add the possibility to push data to Bugsnag asynchronously, relying on Symfony Messenger.
The text was updated successfully, but these errors were encountered: