-
Notifications
You must be signed in to change notification settings - Fork 113
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
Improve Kedro-viz telemetry tracking in the codebase #1900
Comments
Addressed in #1995 |
I have a query about this; I assumed there were two issues with tracking telemetry on Kedro-Viz:
Did we ever understand 1.? |
|
I don't know if this issue is closed though; as we still need to create a proper heap dashboard. A part of this issue is closed: improving tracking to the code. |
@rashidakanchwala Okay, that’s fair. Maybe what would be helpful is if you could complete the description for the GitHub issue and describe what needs to be done, because they can be sub-tickets of this one. Also, this means we should assume that the ratio of Framework to Kedro-Viz users is actually correct, based on what you found? |
Yes, I believe so. Besides, we check this ratio through CLI commands rather than UI interactions. Specifically, we track unique users who run Agree, improve telemetry is more of an epic which we need to break down into multiple tickets. I will do that now. |
closing this as 99 tickets later we have a follow up ticket :) #1999 |
Description
The Kedro-viz telemetry numbers seem very low. This ticket is to revisit telemetry and ensure that tracking is accurate and correct information is being recorded.
Update - Kedro-Viz heap tracking works as expected. However there were number of interactions that were out of date and some new ones that we weren't tracking. We have fixed that now in #1995. Follow up ticket to this is #1999.
Context
Why is this change important to you? How would you use it? How can it benefit other users?
Possible Implementation
(Optional) Suggest an idea for implementing the addition or change.
Possible Alternatives
(Optional) Describe any alternative solutions or features you've considered.
Checklist
The text was updated successfully, but these errors were encountered: