-
Notifications
You must be signed in to change notification settings - Fork 633
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
Comments
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:
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.
It looks as if this is already in place on the Kolibri side, with:
It looks as if this is in place as well: |
I miss here installations done with |
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: |
This Epic was resolved with the release of 0.15.0. |
Get more accurate and better reporting of user devices, including:
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 toFalse
and/or has been invoked usingkolibri services
. Otherwise this will beFalse
.The text was updated successfully, but these errors were encountered: