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'd like to push reconciliation events to sentry. I've already done some investigation and started implementing using the sentry-go library. Happy to make a PR and push my changes upstream if other members would find this integration useful.
The text was updated successfully, but these errors were encountered:
I see that sentry-go is a well maintained package, I'm ok with having Sentry support in Flux. We need to determine what extra fields the Provider needs, I'm not a Sentry user and I can't tell.
@lwj could write here a proposal of how the Provider should look? Thanks
Hi @stefanprodan, thanks for the response. I can give a brief overview:
Sentry uses something called a DSN that gets passed to the SDK to inform it where to send events to. This is just a URL provided by Sentry with the following format:
Sentry users should already be familiar with using this DSN for integration, so I see no reason why we couldn't re-use the existing address field that other providers make use of. This should be the only field we need for the Sentry Provider.
We'd like to push reconciliation events to sentry. I've already done some investigation and started implementing using the sentry-go library. Happy to make a PR and push my changes upstream if other members would find this integration useful.
The text was updated successfully, but these errors were encountered: