A tool I’ve been working on for the past 2 weeks!
You pipe your logs into this tool and it opens a port with a live web UI that performs automatic syntax highlighting on the input according to some heuristics.
It also allows you to filter based on the syntax highlighting engine e.g. @@url will only show logs that contain a URL.
It’s already been helpful for my daily work and some of my coworkers. Happy to field any questions or feature requests!
You can find out by trying the demo here.
One of the explicit non-goals of the project is having a well defined grammar. This is a tool meant for development logs which means we can be significantly more lenient in what and how we highlight.
You’ll find similar highlights in tools like tailspin. Automatic highlighting for HTTP methods, URLs, IPs, numbers, strings, error text, tags, etc.
We don’t rely on a specific structure. We’re highlighting these symbols as they come, regardless of the format they’re presented in.
This reminded me of https://lnav.org/
Yeah, I have a list of alternative tools at https://logpipe.dev/guide/alternatives.html if you’d like to explore other ones.
A tool I’ve been working on for the past 2 weeks! You pipe your logs into this tool and it opens a port with a live web UI that performs automatic syntax highlighting on the input according to some heuristics. It also allows you to filter based on the syntax highlighting engine e.g.
@@urlwill only show logs that contain a URL.It’s already been helpful for my daily work and some of my coworkers. Happy to field any questions or feature requests!
I’m confused. What syntax is it highlighting? Logs are so variable, every logging package I’ve used seems to have a different format.
You can find out by trying the demo here. One of the explicit non-goals of the project is having a well defined grammar. This is a tool meant for development logs which means we can be significantly more lenient in what and how we highlight.
You’ll find similar highlights in tools like tailspin. Automatic highlighting for HTTP methods, URLs, IPs, numbers, strings, error text, tags, etc. We don’t rely on a specific structure. We’re highlighting these symbols as they come, regardless of the format they’re presented in.