Skip to content
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

Visualisation of Data Freshness #12

Open
therealslimjp opened this issue Aug 27, 2024 · 6 comments
Open

Visualisation of Data Freshness #12

therealslimjp opened this issue Aug 27, 2024 · 6 comments

Comments

@therealslimjp
Copy link

I could imagine that it would be useful, to have a tab with visualization of freshness-related statistics, such as graphs of ingestions over last x days, Table Size trends etc.

What do you think? I could start working on it.

If you have other ideas related to this, leave a comment

@rakeshJn
Copy link
Member

Sure, exactly what I have in mind @therealslimjp.

The only thing I want to get opinion of people is - should we stick with Streamlit or move to some other framework like Flask? Let me open an issue on that and discuss there.

@therealslimjp
Copy link
Author

Bildschirmfoto 2024-08-27 um 21 52 43

just wrote a quick mockup, what do you think of something like this?

@therealslimjp
Copy link
Author

also @rakeshJn i need permissions to create branches, can you do this?

@juancappi
Copy link
Collaborator

Hi @therealslimjp, I think the idea looks great. I'd probably also add an equivalent metric for size (i.e. in GBs). Record count it's great, but not always indicative enough. Maybe add another drop down for records/size?

w.r.t. to branches, you need to fork the repo, create a feature branch in your fork and then create a PR off your fork. More details here: https://docs.github.com/en/get-started/exploring-projects-on-github/contributing-to-a-project#making-a-pull-request

@rakeshJn
Copy link
Member

Looks good to me, and yes, both for record count and size. I wonder how we will keep it accurate if table maintenance happens and old snapshots are removed. We will lose history, isn't it?

@therealslimjp
Copy link
Author

therealslimjp commented Aug 28, 2024

Looks good to me, and yes, both for record count and size. I wonder how we will keep it accurate if table maintenance happens and old snapshots are removed. We will lose history, isn't it?

yep, i thought about that too. don't think we can do much against that though. Maybe i'll add just note that it refers to ingested data since compaction (and maybe even limit the datepicker to the first available snapshot? idk yet what's best)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants