up VS lnav

This fx rewrite is very exciting. I'll have to try it. I thought of fx as a wrapper around jq, that allowed quick iteration over building jq scripts. Sort of an Ultimate Plumber [1] but only for jq. It looks like it is now more like a JavaScript processor plus an interactive viewer.

Someone mention Visidata[2]? VisiData is also a TUI that is great on tabular data, and it can work with json. If your JSON is mostly tabular in nature, Visidata does a great job at showing that data and allowing you to explore it. A lot of json I deal with is tabular-like data. There is a great tutorial [3], that can help you get your bearings with Visidata. Once you understand those basics you might want to look at this thread [4] for what commands you can use with json.

[1] Ultimate Plumber: https://github.com/akavel/up

Ultimate plumber can do this.

https://github.com/akavel/up

Been using up for years but this looks nice too

Fun. But I can achieve the same result (I think) with ultimate plumber and regular jq, but without being restricted just to jq. Feel free to correct me.

Up - The Ultimate Plumber makes the best pipes !

Also featured in that thread: https://github.com/akavel/up

For example:

As an alternative allowing the use of any shell command/pipeline on the results interactively, see also: https://github.com/akavel/up

Would https://github.com/akavel/up solve your problem?

Do you have some tricks for how you handle filtering through logs? Or if there could be a tool thst could help you or mitigate your most critical issue[s]?

I found filtering through longs a major pain even for a fully sighted person like me, so I wrote a tool to help me with that, but it's fully in a "TUI" paradigm (i.e. curses-like), so I presume it wouldn't help you much (https://github.com/akavel/up). No promises, given that the tool as is scratched my itch, but I am honestly curious if something similar could reduce your PITA, including whether this specific tool could be made useful for you through some minimal effort on my side.

The code base seems like a good reference as a small Python project.

My fav option in this class of apps: https://lnav.org/ It lets you use journalctl with pipes as requested here: https://github.com/Textualize/toolong/issues/4

For local development, I cannot recommend lnav[1] enough. Discovering this tool was a game changer in my day to day life. Adding comments, filtering in/out, prettify and analyse distribution is hard to live without now.

I don't think a browser tool would fit in my workflow. I need to pipe the output to the tool.

[1] https://lnav.org/

https://lnav.org/ has a feature that single handedly sold me on trying out the fantastic software: An SSH-reachable playground. It's right there above the fold on the first page: ssh://[email protected]

I want to build a similar playground for people who want to get familiar with the tools my Shell Bling Ubuntu repo provides ( https://github.com/hiAndrewQuinn/shell-bling-ubuntu ). Ideally it consists of a series of very simple tasks to get one's feet wet with each tool provided: Using fish's autocompletion, then using fzf's shell keybindings, then using rg instead of grep to search an enormous number of files for a single needle character in a million lines of wheat , and so on.

I have no clue how to do this safely. I've never seen how anyone else does it either. Can anyone provide me some pointers?

It looks like they run an SSH server inside a Docker container defined by this Dockerfile [1]. This uses the ForceCommand directive in the sshd_config file to ensure that a specific command is run when a user connects (rather than the user connecting directly to a shell).

Depending on whether the user connects as the `playground` or `tutorial1` user they interact with a bash script that is either [2] or [3].

[1]: https://github.com/tstack/lnav/blob/master/demo/Dockerfile

[2]: https://github.com/tstack/lnav/blob/master/docs/tutorials/pl...

[3]: https://github.com/tstack/lnav/blob/master/docs/tutorials/tu...

This is really pretty - I do really wish for a good rust replacement for lnav[1] someday.

1: https://lnav.org/

> I also don't see something else I might want: a way to have a different "view" for certain log messages; maybe to switch between filtering/viewing particular ones, maybe to just have line-format be conditional based on the detected format.

Have a look at the following comment on an issue that might be similar to what you're thinking of:

https://github.com/tstack/lnav/issues/1065#issuecomment-1602...

> I guess I can sort of do this based on `module-field`? but I might want it lighter-weight/finer-grained than that.

Unfortunately, the "module-field" does not work for JSON logs at the moment. It's something I should really fix.

Ultimately, lnav has existed for almost two decades now and I use it every day. So, it's always seeing improvements. If you're having a problem with it, file an issue on github. I don't always get around quickly to fixing other folks feature requests / issues, but it tends to happen eventually.

Thanks.