parabol
parabol copied to clipboard
ParabolInc
Remove Sentry in favor of Datadog APM & RUM
Now that we have Datadog RUM on the frontend, we have no reason to keep Sentry. Everything we're sending to Sentry we're already sending to datadog.
Datadog is superior because it can correlate client events with server events, nginx, rethinkdb. It can do client-side session replays, and it's 1 fewer tool that our devs need to learn.
AC
- [ ] Explore datadog & sentry. Determine if datadog receiving all the events that we send to sentry today. If not, create an issue to get us there.
- [ ] Create an issue to replace all calls to sentry with calls to datadog & remove sentry from our app.
- [ ] Create an issue to document how to discover errors in datadog like we do in sentry today
See also #5991 - it would be nice to get that merged before attacking this. It'll help reduce merge conflicts adjusting Sentry.
@mattkrick, as part of the AC, should we include updates to the governance policy 🔒 related to Sentry?
While the full stack trace is now available, I ran into some process issue. Creating and linking a GitHub issue seems not to be possible. This is not too bad, but I did not find a way to assign someone or otherwise mark an issue as being processed. The only thing I found was setting the status from "open" to "ignored". I contacted support about this, maybe there is a better way I could not find.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
I contacted support about this, maybe there is a better way I could not find.
@Dschoordsch curious if you heard back from them?
@nickoferrall Yes, I had heard back from them, there is no way of marking an issue as assigned, i.e. to exclude it from a search filter in the future. I feel like this is a main blocker. I looked again about a month ago and could not find anything new.
