Hey there! We've been having issues where our Meta...
# secoda-support
c
Hey there! We've been having issues where our Metabase resources sometimes do not show up in the lineage. The Snowflake ones always do, but Metabase shows up inconsistently. Please help? 🙂
a
Hey @careful-policeman-58309 Thank you for flagging this. • Are you noticing different resources disappearing or is it a specific resource that disappears from the lineage? • Would you mind providing some examples that we can use to investigate this further? Appreciate the additional details!
👋 1
c
We're noticing that all Metabase resources disappear from the lineage of a Snowflake table. So like for this table (
fct_payments_requests
), there should be a lot of Metabase cards showing downstream. They were showing up last night, but today they're gone. I tried resyncing the Metabase integration and it was unsuccessful. This is a screenshot of how it currently looks on my end!
I am seeing Metabase resources that I know are downstream of
fct_payments_requests
in the catalogue itself. If I click into one of those, the Metabase lineage shows up but the upstream Snowflake tables do not.
a
Hey @careful-policeman-58309 thanks for providing these examples. We're investigating these. To summarize, • Metabase cards are disappearing from lineage of Snowflake objects. (Example: fct_payments_requests) • In that metabase resource itself (e.g., Successful Payments Yesterday) - the Snowflake lineage also does not show up. Just to confirm - did it show up before?
c
I'm honestly not sure if the Snowflake lineage used to show up in the Metabase resource.
We typically look at the Snowflake table and work downstream from there. I just figured it should be there, but maybe that's not the case!
Is there any update from the investigation?
a
I see - thank you for the details, Dayna! Our team is working on improvements to address this. We'll keep you posted on when these are deployed - appreciate your patience!
c
Sounds great - thank you!