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
Review of the telemetry events #179
Milestone
Comments
Notes from meeting this morning:
|
deboer-tim
added a commit
to deboer-tim/podman-desktop-extension-bootc
that referenced
this issue
Apr 5, 2024
Exposed the telemetry logger from the extension, and changed build-disk-image.ts to use it instead of its own. While doing this I noticed that logUsage was being called before and after the build, so I removed the first to avoid double-counting. Adds telemetry event when pulling images. The intent here is to show how often users pull the example but will also trigger when pulling the image builder itself, which might also be useful. Exposes telemetry logging to frontend, and sends an event when someone clicks on the button to go to the Build page. Part of containers#179. Signed-off-by: Tim deBoer <git@tdeboer.ca>
cdrage
pushed a commit
that referenced
this issue
Apr 5, 2024
* feat: add telemetry to pull, goto build page Exposed the telemetry logger from the extension, and changed build-disk-image.ts to use it instead of its own. While doing this I noticed that logUsage was being called before and after the build, so I removed the first to avoid double-counting. Adds telemetry event when pulling images. The intent here is to show how often users pull the example but will also trigger when pulling the image builder itself, which might also be useful. Exposes telemetry logging to frontend, and sends an event when someone clicks on the button to go to the Build page. Part of #179. Signed-off-by: Tim deBoer <git@tdeboer.ca> * chore: telemetryLogUsage and logError Responding to PR review: rename API to telemetryLogUsage so that it's clear, and expose logError() while we're at it. Signed-off-by: Tim deBoer <git@tdeboer.ca> --------- Signed-off-by: Tim deBoer <git@tdeboer.ca>
Telemetry in, charts updated, but forgot to list the implied charts required for the new telemetry. Will add these, then close. |
cbr7
pushed a commit
to cbr7/podman-desktop-extension-bootc
that referenced
this issue
Apr 11, 2024
* feat: add telemetry to pull, goto build page Exposed the telemetry logger from the extension, and changed build-disk-image.ts to use it instead of its own. While doing this I noticed that logUsage was being called before and after the build, so I removed the first to avoid double-counting. Adds telemetry event when pulling images. The intent here is to show how often users pull the example but will also trigger when pulling the image builder itself, which might also be useful. Exposes telemetry logging to frontend, and sends an event when someone clicks on the button to go to the Build page. Part of containers#179. Signed-off-by: Tim deBoer <git@tdeboer.ca> * chore: telemetryLogUsage and logError Responding to PR review: rename API to telemetryLogUsage so that it's clear, and expose logError() while we're at it. Signed-off-by: Tim deBoer <git@tdeboer.ca> --------- Signed-off-by: Tim deBoer <git@tdeboer.ca> Signed-off-by: Vladimir Lazar <vlazar@redhat.com>
#288 is closed, I believe we can close this now? |
I've verified all events are being output and appear in Segment, and have drafts of all charts. Closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your enhancement related to a problem? Please describe
We'd like to review the telemetry events we are reporting to ensure we have proper information about how the users are using the extension and where they are eventually facing challenges
Describe the solution you'd like
We'd like to review the telemetry events we are reporting to ensure we have proper information about how the users are using the extension and where they are eventually facing challenges
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: