I'm not sure how familiar you are with segment.io, but it's a super easy data piping service. So we use Segment to define all of our events across our stack, front-end, middle-ware, backend and then we just connect segment to sentry using the integration they provide. FWIW, we use segment for all of our data piping needs...errors, interaction tracking, traffic analytics, etc. This way we can not only have the errors show up in sentry for us to review, but we can also review in other services where in an event stream any given user ran into the error for easier debugging.
How do you get errors to other services in Segment?
Did you write some custom code to catch errors and then send them as segment's track calls?
We use Sentry with Segment, but on client segment just loads sentry and the errors are caught by sentry only, they do not appear in other integrations.
Interesting, thanks for sharing that. What other services are you using? Is there anything I can read up on for this kind of operational stuff? It would be interesting to learn about the landscapes of tools people use for their production setups.
We use a variety of tools, and often when we add a new tool it's because we review the integrations for segment and discover a service that we can leverage. For a good starter setup though, I really enjoy segment, sentry, mixpanel, and heap.io. We use a few other services, but when it comes to troubleshooting for customers these are our main goto services.
