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

Feature request: table viewer #3

Open
134130 opened this issue Mar 19, 2024 · 4 comments
Open

Feature request: table viewer #3

134130 opened this issue Mar 19, 2024 · 4 comments

Comments

@134130
Copy link

134130 commented Mar 19, 2024

  • I want to see json logs as table formatted
  • json columns can be editable(selectable) on table header
  • shows only selected json columns' data
@soorajshankar
Copy link
Owner

Could you provide a sample? I mean logs are generally different from every use case - I am trying to understand if we can find a generic pattern or a custom parser that a user can setup. if the parsing is done, we can do a lot more in visualising the logs- which would be super awesome!

@134130
Copy link
Author

134130 commented Mar 19, 2024

  • I've customized this project's code, without scalability, for near future demo event.

    • image
  • The really simple example is this one: http://json2table.com/

  • But I think it will be very attractive when table heads (columns) are selectable.

  • Columns : column will be selectable and sortable. structed JSON log's key will be column, even once appeared.

@soorajshankar
Copy link
Owner

Looks nice, what if there is a configuration on the web app side- a pure JS function that takes logline string and returns an object- so the react-table can take the Object keys as column headers and values on rows.

Why not do this automatically?

Because my concern is that, the loglines are really different in every usecase, and hence introducing defaults will introduce bugs - but if we make this a configuration then users would get more flexibility - thoughts?

@soorajshankar
Copy link
Owner

I also feel like it's time to separate the frontend to a proper npm project :)

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

2 participants