3 ms·
It's definitely not just crashes— your documentation talks all over the place about custom events, extra data blobs, breadcrumbs, etc: https://docs.sentry.io/p
by mikepurvis 5y ago
It's definitely not just crashes— your documentation talks all over the place about custom events, extra data blobs, breadcrumbs, etc:
https://docs.sentry.io/product/cli/send-event/ https://docs.sentry.io/product/cli/send-event/
Other places discuss sending "info"-level log events:
https://docs.sentry.io/platforms/python/guides/logging/ https://docs.sentry.io/platforms/python/guides/logging/
These things aren't necessarily bad, but they're 100% the building blocks for various forms of badness, and I can fully understand track-free users just saying no to all of it.
In any case, the solution for Sentry-the-company is just to have a separate domain for receiving events, so getting that blocked doesn't block your corporate landing page.
- Aeolun 5y agoWhy would someone use Sentry for that when stuff like OpenReplay exists. It’s like trying to hammer your nail in with a screwdriver.
- mikepurvis 5y agoI don't think you would if your upfront goal was "telemetry" and you actually evaluated solutions for that. But if you had the Sentry pipeline in place already for crash reports, it would be very easy to slide into using it for tracking other kinds of custom events.