- As an MVP, POST to EventGate by overriding globalOptions.shouldSendCallback as @Tgr suggests in T217142#5135708
- Update to newer Raven client
- Stop fighting Raven's install window.onerror hijack, and just use captureMessage without install: https://github.com/getsentry/sentry-javascript/issues/316#issuecomment-262385903
- Estimate how long a custom client would take to write (while I'm fiddling with this, I might as well spend a little time thinking about it)
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | phuedx | T217142 [Proposal] Use the Kafka-Logstash logging infrastructure to log client-side errors | |||
| Declined | Milimetric | T222180 Point Extension:Sentry to EventGate (beta) |
Event Timeline
Comment Actions
I just glanced at this quickly and it seems to me we should use the new client from the start, because it solves some problems that make the original code complicated. And I feel like it's a better test. @Tgr, let me know if you disagree.
Comment Actions
Well, the original code already worked around those problems so it depends on how much time you want to spend on this. If you want to use the old code and just point it to EventGate, that's a one-liner (assuming there is a one-liner for sending something to EventGate - Sentry's default mechanism puts the whole JSON into a GET parameter, which is problematic in many ways, so you probably don't want to use that). If you do have the time to upgrade the client, that would certainly be nice.
Comment Actions
As far as I understand, our experiments with Extension:Sentry were replaced by the Client errors data pipeline.