Skip to content
This repository has been archived by the owner on Jun 8, 2020. It is now read-only.

Accessing and interpreting client-side telemetry #142

Closed
MaxDiz opened this issue Sep 16, 2019 · 1 comment
Closed

Accessing and interpreting client-side telemetry #142

MaxDiz opened this issue Sep 16, 2019 · 1 comment
Labels
client-side telemetry user analytics improvements Type: Improvement Make something better

Comments

@MaxDiz
Copy link

MaxDiz commented Sep 16, 2019

As a product team member, I want clearer definitions of client-side telemetry data access and output, so that I can effectively measure how our product performs and how users are engaging with features.

Requesting documentation on:

  • Which data sets are available for queries and when they became available (ie earliest possible query date)
  • How to perform client-side telemetry SQL queries
  • Instance telemetry clarification on data fields, measurement units, and frequency of data availability
  • Aggregate telemetry clarification on data fields, measurement units, and frequency of data availability

This is a follow-up to medic/medic-projects#6882

@garethbowen garethbowen added the Type: Improvement Make something better label Sep 16, 2019
@MaxDiz MaxDiz added the client-side telemetry user analytics improvements label Oct 4, 2019
@MaxDiz MaxDiz added client-side telemetry user analytics improvements and removed client-side telemetry user analytics improvements labels Oct 8, 2019
@garethbowen garethbowen self-assigned this Nov 28, 2019
garethbowen added a commit that referenced this issue Dec 2, 2019
@garethbowen
Copy link
Member

Done. No AT required.

@garethbowen garethbowen removed their assignment Dec 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
client-side telemetry user analytics improvements Type: Improvement Make something better
Projects
None yet
Development

No branches or pull requests

2 participants