May - Analytics: Tracking issue

[cbart]

Tasks

Preview Give feedback

1. (P0) Streamline user to instance mapping sourcegraph#60918
   +0
2. (P0) [strat:P] Display new chat/commands metrics sourcegraph#60562
   +0
   
3. (TBD) Associate instance URLs with accounts sourcegraph#59274
   +0
   
4. (P1) Improve UI to navigate from Cody Analytics to the instance admin and vice versa sourcegraph#60427
   +0
   
5. (P1) Count tokens for non-cody gateways usage sourcegraph#59271
   +0
   
6. (Backlog) Intent analysis sourcegraph#59272
   +0
7. Figure out how intent classification could work through the agent. sourcegraph#59523
   +0
8. (P0) Fix the Cody Analytics for Telemetry v2 sourcegraph#61011
   +0
   
9. Cody Analytics: Add Time Selector sourcegraph#61039
   feedback +1
   
10. Cody clients: provide client name and version in the completion endpoint requests sourcegraph#62116
    1 of 5
    +0
11. Split single-line and multi-line latencies sourcegraph#62517
    +0
12. Billing DAU vs Product Usage DAU sourcegraph#62516
    +0
13. Split data between IDEs and Web sourcegraph#62621
    +0
14. Add Thumbs up and Thumbs down info on Cody Analytics sourcegraph#62622
    0 of 3
    +0

[cbart]

We sketch this for 3 weeks as opposed to planned 2 today as the middle week is Merge and we'll likely pause on the effort during that time.

[cbart]

@aramaraju it seems we've finished work on Analytics this iteration. Is it OK if I move remaining items to an analytics backlog tracking issue and close this?

[aramaraju]

@cbart Yes, we can move open items to the backlog and close the May issue IMO