DevX: Q2B2 DevX product analytics tracking issue
Created by: marekweb
Problem
We're improving how we collect and aggregate analytics and metrics that are relevant to DevX work.
We need these analytics to better inform DevX team work, and also to be able to better inform external stakeholders about the outcomes of DevX work.
Scope
-
Boundaries
- Confirm our preferred choice of tooling for analytics (decisions about OkayHQ, Honeycomb)
- Identify the metrics that we're tracking
- Transfer metrics from deprecated tooling to our new preferred tooling
- Idenfity new metrics that we're not yet tracking but we'd like to track
-
Definition of done
- We have a clear idea of which metrics we're collecting and which tool to access them
- We make metrics available in an accessible location to stakeholders outside of the team
-
Rollout Plan
- Communicate our preferred tooling for analytics, with explanation for why we're choosing it, and which tools we will be dropping.
- Communicate which DevX metrics we're tracking and how they might be useful outside of the team
- Communicate which DevX metrics are informing our decisions internally to the team
Tracked issues
@unassigned
-
https://github.com/sourcegraph/sourcegraph/issues/37808 -
https://github.com/sourcegraph/sourcegraph/issues/37809 -
https://github.com/sourcegraph/sourcegraph/issues/40806 -
https://github.com/sourcegraph/sourcegraph/issues/40807
@bobheadxi
Completed
-
( 🏁 1 day ago) https://github.com/sourcegraph/sourcegraph/issues/37810
@marekweb
-
https://github.com/sourcegraph/sourcegraph/issues/39505 -
https://github.com/sourcegraph/sourcegraph/issues/39512