Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Collect enhanced telemetry data #7960

Closed
rtibbles opened this issue Apr 6, 2021 · 4 comments
Closed

Collect enhanced telemetry data #7960

rtibbles opened this issue Apr 6, 2021 · 4 comments
Labels

Comments

@rtibbles
Copy link
Member

rtibbles commented Apr 6, 2021

Get more accurate and better reporting of user devices, including:

  • Browser information of client devices
  • Accurate installer information
  • Information about apps and other 'launch' modes (e.g. cherrypy, uwsgi, gunicorn, apache)
  • Project specific tagging so we can trace more information about projects we are working directly with

Installer information spec:
https://docs.google.com/spreadsheets/d/1EpN4yIO9H0qkP0pY6jiEtfQIdyrEPChs3aDZwOMupcI/edit#gid=0

*If the task runner has been invoked either with CHERRYPY_START set to False and/or has been invoked using kolibri services. Otherwise this will be False.

@jamalex
Copy link
Member

jamalex commented Oct 29, 2021

Accurate installer information

I have copied and updated the table in the original issue description into this spreadsheet, and bolded the places where I am proposing something different than what was laid out there:
https://docs.google.com/spreadsheets/d/1EpN4yIO9H0qkP0pY6jiEtfQIdyrEPChs3aDZwOMupcI/edit#gid=0
(important notes have been added to the last column)

Information about apps and other 'launch' modes (e.g. cherrypy, uwsgi, gunicorn, apache)

We're folding the "app" info into the installer field, as they're tightly coupled. Determining that gunicorn, apache, etc are being used doesn't seem feasible, given that in those scenarios the task runner would need to be run separately anyway, so it would be hard to pick it up from the context of the ping.

Project specific tagging so we can trace more information about projects we are working directly with

It looks as if this is already in place on the Kolibri side, with:
"project": conf.OPTIONS["Deployment"]["PROJECT"]

Browser information of client devices

It looks as if this is in place as well:
"dis": usersess_devinf,

@jredrejo
Copy link
Member

I miss here installations done with pex and with pip.

@jamalex
Copy link
Member

jamalex commented Oct 29, 2021

The table that was in the initial issue description was not the latest -- I updated the table (including adding pex/pip) in the spreadsheet linked in my last comment:
https://docs.google.com/spreadsheets/d/1EpN4yIO9H0qkP0pY6jiEtfQIdyrEPChs3aDZwOMupcI/edit#gid=0
(so that should be considered the canonical values)

@rtibbles
Copy link
Member Author

This Epic was resolved with the release of 0.15.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants