-
Notifications
You must be signed in to change notification settings - Fork 112
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 and explain frontend telemetry #2140
Comments
hey @astrojuanlu thanks for drafting all these requirements and questions, very helpful to follow them. Please see my reply as below:
|
💯!
Exactly what we needed 👍🏼
👍🏼
Understood 👍🏼
In the raw table (the one that gets ingested directly from Heap to Snowflake), the column will unfortunately have to still be called |
this is perfect, thank you @astrojuanlu. I've created two tickets to address the Kedro-Viz version issue and to enable tracking on the demo page. Regarding creating intermediate tables to address the DATA_HEAP_EVENT, I'm uncertain if it's worth further effort since I managed to add a column in Tableau that filters through the data hierarchy to return only data-test values. It's a bit hacky, but it works for now. Let me know your thoughts! |
Yeah, i think there's no easy way to do this. Heap has suggested data* attributes or aria-labels and I think it doesn't give us the information directly hence we need to look for it under HREF/Hierarchy column. Some details here - https://help.heap.io/data-management/react-dom-minification/general-strategies-for-using-heap-with-a-minified-dom/ |
I'm confused, @rashidakanchwala could you elaborate? Is this related to kedro-org/kedro-plugins#923, #2158, something else? |
neither, it's related to @Huongg's comment here
|
Ah got it. Creating a dynamic column in Tableau is a good quick and dirty solution but eventually the Single Source of Truth should be a "gold" table in Snowflake, see https://lakshmanok.medium.com/what-goes-into-bronze-silver-and-gold-layers-of-a-medallion-data-architecture-4b6fdfb405fc That's out of the scope for this ticket anyway. |
From the original list on #2140 (comment),
Syncing some of these events to Snowflake might require an extra step, if needed we can have a look together. Finally there's an ongoing investigation on the lack of One more clarification from my side. I get that
or
Could you clarify? |
#2158 - that's the issue. We should definitely look at HEAP_HIERARCHY and regex this bit |
I think there's already follow-up issues for everything, thank you! |
In the context of kedro-org/kedro-devrel#151 we're trying to understand Kedro Viz frontend telemetry.
This is what we need:
if this is not possible, then we have to decide between "opening the Kedro Viz frontend" == "launching $ kedro viz run" OR "opening the Viz frontend" == ">=1 click event anywhere"
you can either catalogue all elements and give us the list, or just tell us how to know whether an element belongs to Experiment Tracking
Here's what we're currently seeing on Snowflake:
I have several questions:
Could you double check that frontend telemetry is flowing?
HEAP_HIERARCHY
changes across versions (the CSS and HTML change). Could we add that to the table somehow?DATA_ATTRIBUTE_DATA_HEAP_EVENT
mean?DATA_HEAP_EVENT
is empty in all cases. Is that intended?https://demo.kedro.org/
in the top list of landing pages, which is interesting to say the least:Is telemetry enabled for our demo site? If not, can we open a ticket to enable it? And if it's indeed enabled, should we investigate why it's not flowing?
The text was updated successfully, but these errors were encountered: