-
-
Notifications
You must be signed in to change notification settings - Fork 623
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace Sentry integration with Segment #1640
Comments
@unn The first wheezing Segment events went through: https://app.segment.com/drud/sources/ddev_local_dev/debugger BUT... I'm baffled how we'll use that. What of those thousands of destinations would be useful? Obviously without valid destinations we don't have any use for this service. Note that we don't have to have segment push to sentry, we can just push to both of them. |
Right you are, in the dev source, we probably won't have a destination but the production one will 100% be connected to Amplitude. I'll get it configured, at the moment there isn't much to see there. |
One note @unn, I don't know how to identify users (which is absolutely required by segment) except by host id. So what I did was use a hashed hostid. Other thoughts are solicited... |
It looks to me like the hashed hostid is a great fill-in there? It's anonymized by the hash, etc. What do you think? |
Makes sense to me. |
@unn i see you connected prod to amplify, but I'm pretty much blocked on this until I can see how the data will be used so I can send useful stuff. Can we do a dev setup (or use prod for now), and get me access to Amplify? Thanks. |
Invite sent. Though I'll note that without data Amplitude is a little bare bones, since it's hard to setup dashboards without having any data there yet. Dashboard items I'm planning on creating:
|
Is your feature request related to a problem? Please describe.
Sentry is a great service for error and exception handling, but it's really not meant to be an audience management or a data analytics tool. We have integrated or plan on integrating several of our tools with Segment. It makes sense to utilize the same tools across product lines where possible.
Describe the solution you'd like
Replace the analytics gathering integrations currently handled by Sentry with Segment.
Additional context
It appears from Segments documentation that they don't yet support server (server here because of golang) installs. See https://segment.com/docs/destinations/sentry/ We'll probably have to continue to implement the exception and error tracking until a time when Segment can support server-based Sentry. I've reached out to both companies to inquire about time lines.
https://drud.slack.com/archives/C45DF87JT/p1559668781009000
The text was updated successfully, but these errors were encountered: