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

Stream Inspector #17

Closed
5 tasks done
neovintage opened this issue May 3, 2021 · 7 comments
Closed
5 tasks done

Stream Inspector #17

neovintage opened this issue May 3, 2021 · 7 comments
Assignees
Labels
feature New feature or request roadmap Planned for a future release
Milestone

Comments

@neovintage
Copy link
Contributor

neovintage commented May 3, 2021

The goal is to give folks the ability to see what's happening inside the stream. This is not like tail. This is more like peek. Pull out some information from the stream so that a developer can see the data and data types.

@lovromazgon lovromazgon transferred this issue from another repository Jan 11, 2022
@lovromazgon lovromazgon added this to the Backlog milestone Jan 11, 2022
@lovromazgon lovromazgon added the feature New feature or request label Jan 11, 2022
@neovintage neovintage added the roadmap Planned for a future release label Feb 18, 2022
@uchennakevinm1 uchennakevinm1 modified the milestones: Future, 0.4.0 Oct 18, 2022
@hariso hariso assigned hariso and unassigned hariso Oct 20, 2022
@lyuboxa
Copy link
Contributor

lyuboxa commented Oct 21, 2022

Inspector will be nice, but I will raise you a REPL for this, it will be magnificent.

@neovintage
Copy link
Contributor Author

@lyuboxa what would a repl look like? Would you have to create a "conduit cli" to make this possible?

@lyuboxa
Copy link
Contributor

lyuboxa commented Oct 26, 2022

I think any tooling that can be used to inspect data real time and does not involve explicit parsing will be useful. When @hariso and I were discussing this something like this came to mind:

$ conduit-cli
> pipelines
<... print list of pipelines>
> c  = pipeline["abc"].connector["source"]
> c.peek(1) 
-> <message in structured format>
> c.processors["anonymize"].Peek(1)
-> <message in structured format> 

I think an interactive REPL will be useful, a console or whatever you want to call it.

@lovromazgon
Copy link
Member

@lyuboxa A REPL doesn't sound very composable to me 😕 Why not rather provide a simple CLI command to get the records? This would let you compose it with other tools like grep & co. Example:

$ conduit-cli inspect id:of:my:component --limit 2
<message>
<message>

Sidenote: I think it's a bit off-topic to talk about a CLI/REPL in this issue, it sounds like a whole separate feature by itself.

@lyuboxa
Copy link
Contributor

lyuboxa commented Oct 27, 2022

A REPL doesn't sound very composable to me .

Does it have to be? REPL are interactive tools for evaluation, not unix commands. Both options have their merits.
Former is more suitable for interactive work (which CLI is not tbh, but it does need a way to enter an interactive session).
However, if you only want to dump data and move on, then this is likely not the most optimal solution.

Sidenote: I think it's a bit off-topic to talk about a CLI/REPL in this issue, it sounds like a whole separate feature by itself.

Yup for sure.

@hariso
Copy link
Contributor

hariso commented Oct 28, 2022

Sidenote: I think it's a bit off-topic to talk about a CLI/REPL in this issue, it sounds like a whole separate feature by itself.

Yup for sure.

Here's a separate issue for that: #697.

@hariso
Copy link
Contributor

hariso commented Jan 27, 2023

All the tasks are done, closing the issue.

@hariso hariso closed this as completed Jan 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request roadmap Planned for a future release
Projects
Archived in project
Archived in project
Development

No branches or pull requests

5 participants