aj-codecov
commented
4 days ago From Sentry's side of things on how they implement Amplitude: https://www.notion.so/sentry/Amplitude-Knowledge-Sharing-2071ebb9a1c741ecb485cc0f266195ae
Sentyr dev docs on how they add events: https://develop.sentry.dev/development/analytics/
From Spencer: Sentry metrics is no more and we are now without a place to dump product metrics. With our current situation I feel like I'm more or less running blind on feature releases and I want to resolve that! For example, with the new header release, the only metrics I had to go on were feature flag evaluation numbers in LaunchDarkly and any Sentry issues that popped up.
After talking with Rohit, I think a solid path forward will be to adapt his onboarding metrics solution to work for more generic usecases. This will let us query the metrics in metabase, which works well for technical folks. Katia suggested I bring this up with you as a potential project for next quarter! There's not a ton of work here, but enough to warrant a small OKR I think.
Rough work required: Remove requirement to be logged in for metrics to work. Remove restriction allowing only one metric per owner of each key. Establish usage patterns in Gazebo and metabase to function as references for future metrics. Bonus: API should be accessible from not just Gazebo (i.e., vscode extension, browser extension, slack integration, etc.) Those top two items will require an investigation and likely will require some rearchitecting of the current solution. In the worst case, we'd have to rewrite a large chunk of the current code (fortunately, there's not a lot!)