Skip to content
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

Closed
unn opened this issue Jun 5, 2019 · 8 comments
Closed

Replace Sentry integration with Segment #1640

unn opened this issue Jun 5, 2019 · 8 comments

Comments

@unn
Copy link
Contributor

unn commented Jun 5, 2019

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

@rfay rfay added this to the v1.10 milestone Jun 28, 2019
@rfay
Copy link
Member

rfay commented Jul 1, 2019

@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.

@unn
Copy link
Contributor Author

unn commented Jul 2, 2019

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.

@rfay
Copy link
Member

rfay commented Jul 2, 2019

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...

@unn
Copy link
Contributor Author

unn commented Jul 3, 2019

@rfay
Copy link
Member

rfay commented Jul 3, 2019

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?

@unn
Copy link
Contributor Author

unn commented Jul 8, 2019

Makes sense to me.

@rfay
Copy link
Member

rfay commented Jul 8, 2019

@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.

@unn
Copy link
Contributor Author

unn commented Jul 8, 2019

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:

  • Monthly active users (MAU)
  • OSes
  • Median time to upgrade
  • Versions in the wild

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants