Conversation
| ### CLI Interface | ||
|
|
||
| ``` | ||
| logcat --key <KEY> [OPTIONS] |
There was a problem hiding this comment.
honestly I never really liked Kafka's approach to this. I totally agree we need a utility but having a million different tools to interact with Kafka was always a pain.
I much prefer the traditional RDBMS approach where you have one REPL interface that you can use to SELECT/INSERT/DELETE etc... (and configurations etc...). It's a nicer UX.
There was a problem hiding this comment.
I'm fine with that. I agree we don't want a jillion separate utilities.
There was a problem hiding this comment.
One tool would be better, and perhaps this tool can evolve into that. I can see the case for non-repl mode, if you want to pipe stuff into or out of the tool, etc.
So perhaps we should just make it a more neutral name, something like logcli or something. Then it can add a repl mode and more functions.
There was a problem hiding this comment.
I think something repl-like is good enough for what I need right now. The non-repl stuff is useful too, but could come later.
samsond
left a comment
samsond
left a comment
There was a problem hiding this comment.
Looks good overall. I left two small review comments.
|
|
||
| ## Open Questions | ||
|
|
||
| - Should the tool be named `logcat` or `logdbcat` to avoid confusion with Android's logcat? |
There was a problem hiding this comment.
Tiny naming suggestion: odlog might be worth considering here
| ## Goals | ||
|
|
||
| - Read entries from a log by key | ||
| - Support tailing/following with configurable poll interval |
There was a problem hiding this comment.
I noticed the roadmap mentions tail following “without polling,” while this RFC proposes polling with an interval. Are these intended to describe the same capability, with polling as an initial implementation, or is the roadmap pointing to a different future mechanism?
4 participants
It's useful to have simple cli tool to read from a log.