pwru
lnav
Our great sponsors
pwru | lnav | |
---|---|---|
7 | 75 | |
2,464 | 6,686 | |
6.9% | - | |
9.1 | 9.5 | |
1 day ago | 3 days ago | |
C | C++ | |
Apache License 2.0 | BSD 2-clause "Simplified" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pwru
- GitHub - cilium/pwru: Packet, where are you? -- eBPF-based Linux kernel networking debugger
- cilium/pwru: Packet, where are you? -- eBPF-based Linux kernel networking debugger
-
Packet, where are you? – eBPF-based Linux kernel networking debugger
if you have a recent enough kernel, this change https://github.com/cilium/pwru/pull/148 means that it will print the reason the packet was dropped in the output - see https://lwn.net/Articles/885729/
There's a whole heap of reasons a packet can be dropped:
-
A list of new(ish) command line tools – Julia Evans
[pwru](https://github.com/cilium/pwru) is a fun new tool from the Cilium folks for tracing network packets in the kernel. Like tcpdump but it shows you the full path including kernel syscalls. Lets you debug much deeper than "when the packet gets to this port it gets dropped".
-
Better visibility into Linux packet-dropping decisions
I recently came across another useful utility for debugging unexpected packet drops - PWRU[0] (Packet, Where Are You) by Cilium.
It uses eBPF to try to trace the path of the packet through the kernel. Haven't needed to use it yet, but it could have saved me a lot of trouble in the past.
[0]: https://github.com/cilium/pwru
lnav
- FLaNK Stack 26 February 2024
- LNAV – The Logfile Navigator
-
Toolong: Terminal application to view, tail, merge, and search log files
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
-
Logdy.dev – web based logs viewer UI for local development environment
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/
- Textanalysistool.net
- Ask HN: What apps have you created for your own use?
-
Ask HN: How does `lnav` run its playground which you can just SSH into?
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...
-
Show HN: Tailspin – A Log File Highlighter
This is really pretty - I do really wish for a good rust replacement for lnav[1] someday.
1: https://lnav.org/
-
Structured Logging with Slog
> 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.
What are some alternatives?
parca-agent - eBPF based always-on profiler auto-discovering targets in Kubernetes and systemd, zero code changes or restarts needed!
lightproxy - 💎 Cross platform Web debugging proxy
fsmon - monitor filesystem on iOS / OS X / Android / FirefoxOS / Linux
dive - A tool for exploring each layer in a docker image
libbpf - Automated upstream mirror for libbpf stand-alone build.
glow - Render markdown on the CLI, with pizzazz! 💅🏻
bpfcov - Source-code based coverage for eBPF programs actually running in the Linux kernel
GoAccess - GoAccess is a real-time web log analyzer and interactive viewer that runs in a terminal in *nix systems or through your browser.
conio-for-linux - Conio.h for linux
up - Ultimate Plumber is a tool for writing Linux pipes with instant live preview
nnn - n³ The unorthodox terminal file manager