afterSend callback with Error Id

[killia15]

I'd like to have access to the error Id so that I can generate the link and send it off to other services. From looking at the Bugsnag Error Reporting API docs, a successful response comes back with the Bugsnag-Event-ID. Could we expose that?

I see a mention of an afterNotify callback on #35, but in this case I'm looking for the id, rather than just the fact that it was successfully logged.

[abigailbramble]

@killia15 - Thank you for your comments. This is now raised in our roadmap.

[shaoshiva]

Hello,

Is there any news for this feature? If we could retrieve this ID, we could display it to the user so that he can communicate it to the support team and thus allow us to easily find the event in Bugsnag.

[xljones]

Hi @shaoshiva, not just yet I'm afraid. However, in order to link your user to the event in Bugsnag, you can generate a custom UUID for the user and link it to your event as custom metadata in your configuration, https://docs.bugsnag.com/platforms/javascript/#custom-diagnostics or through a beforeSend callback: https://docs.bugsnag.com/platforms/javascript/customizing-error-reports/#adding-a-callback You can then add a custom filter to search through your metadata. Note that custom filters are only available on our Standard and Enterprise plans. --Xander

[shaoshiva]

Hello Xander,

Thanks for the quick reply. What you propose is not an ideal solution because we have to integrate an additional library to our project in order to generate a UUID, but that will do the job in the meantime 👍

[bendulum]

Any news on this? This would be very helpful and more straight forward than the UUID workaround.

[xljones]

Hi @bendulum, I'm afraid I don't have any updates to reported on this just yet. It's something that's still on our roadmap though 😊

[sibljon]

Any progress? It seems like it would be straight-forward to add, given that there is now an event callback on Bugsnag.notify()

[johnkiely1]

Hi @sibljon, This is still on the backlog. No updates as yet, other priorities have meant we haven't worked on this yet.