Logria
seaoflogs
Logria | seaoflogs | |
---|---|---|
2 | 1 | |
22 | 6 | |
- | - | |
10.0 | 10.0 | |
about 1 year ago | over 2 years ago | |
Rust | HTML | |
GNU General Public License v3.0 only | MIT 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.
Logria
-
How to "Stream" ChildStdout w/Tokio
I had a similar problem and ended it using a mpsc queue queue in a separate thread from my app to read from stderr and stdout.
-
Julia Evans: Tips for Analyzing Logs
I found that most of the "analysis" I perform ends up essentially just performing a search, but I never liked how `tail .. | grep ...` required you to run a new command to change the search criteria. I ended up prototyping my own tool for this [0], which is currently in alpha.
[0]: https://github.com/ReagentX/Logria
seaoflogs
-
Julia Evans: Tips for Analyzing Logs
I wrote https://github.com/ljw1004/seaoflogs - an interactive filtering tool, for similar ends to what's described here. I wrote it because my team was struggling to analyze LSP logs (that's the protocol used by VSCode to communicate with language servers). But I made it general-purpose able to analyze more log formats too - for instance, we want to correlate LSP logs with server logs and other traffic logs.
(1) I wanted something where colleagues could easily share links in workplace chat with each other, so we could cooperatively investigate bugs.
(2) For LSP we're often concerned with responsiveness, and I thought the best way to indicate times when viewing a log is with whitespace gaps between log messages in proportion to their time gap.
(3) For LSP we have lots of interleaved activity going on, and I wanted to have visual "threads" connecting related logs.
(4) As the post and lnav say, interactivity is everything. I tried to take it a step further with (1) javascript, (2) playground-style updates as you type, (3) autocomplete which "learns" what fields are available from structured logs.
My tool runs all in the browser. (I spent effort figuring out how people can distribute it safely and use it for their own confidential logs too). It's fast enough up to about 10k lines of logs.
What are some alternatives?
tracing - Application level tracing for Rust.
color-prefix-pipe - colorize terminal output by prefix
logview - Emacs mode for viewing log files
stern - ⎈ Multi pod and container log tailing for Kubernetes -- Friendly fork of https://github.com/wercker/stern
lnav - Log file navigator