Live data from Hacker News

Show HN: Piping logs, visualizing in a web app – just suffix "| npx logscreen"

github.com

31–40 of 81 posts

Re: Show HN: Piping logs, visualizing in a web app – just suffix "| npx logscreen"

#31
post #26

Earlier quoted context omitted.

As much as I love to hate on chatgpt engineer, the code is definitely okay; not much difference from a project you would write quickly in a single weekend.

The first thing that struck me when I looked at some of the code was: I'm not saying that humans never come up with this kind of crap, but it feels like it's going to be a LOT more common the more we resort to AI. I wonder if "... and make the code easy-to-read so that it's maintainable in future" is ever included in prompts for LLM-generated code.

that's the horror of Tailwind for you, which is different from the horror of AI

Re: Show HN: Piping logs, visualizing in a web app – just suffix "| npx logscreen"

#32
post #14

Is there a benefit over command | vim - ? I love doing that, because then I get all the power of Vim to look at the output. Search, regex search, sorting, bookmarks, counting, macros ... I started to write output that is indented, so I can use Vim's folding to comfortably look at complex data. For example if you have entries like this: 2023-04-12 17:22 Sighted and UFO Location: 27.1742424 12.137234 Temperature: 24°C…

I think this is more designed for streamed output rather than viewing files. Vim doesn't seem to support that, in fact it just says "Vim: Reading from stdin..." forever.

Also it’s not as snappy when you cross the 1GB limit, although it does work, mostly.

Re: Show HN: Piping logs, visualizing in a web app – just suffix "| npx logscreen"

#33

Congrats on launching! Its interesting to see that ChatGPT is able to build something I've been working on ( https://logdy.dev ) for last two months. I guess new era is around the corner then.

Tbf your tool looks 110% more useful and well built than a simple single screen showing the logs with an in-browser search. Keep at it!

Re: Show HN: Piping logs, visualizing in a web app – just suffix "| npx logscreen"

#34
post #32

Earlier quoted context omitted.

I think this is more designed for streamed output rather than viewing files. Vim doesn't seem to support that, in fact it just says "Vim: Reading from stdin..." forever.

Also it’s not as snappy when you cross the 1GB limit, although it does work, mostly.

With a quick look at the code I'm pretty sure this WebUI also wouldn't be snappy along before that.

Re: Show HN: Piping logs, visualizing in a web app – just suffix "| npx logscreen"

#35
I'm not super familiar with express but this seems to be listening on external interfaces as well:

https://github.com/soorajshankar/logScreen/blob/f8b29aaef428...

So this will be sharing your logs with the world if you run this outside of a trusted network. (And personally I avoid trusting any networks)

Re: Show HN: Piping logs, visualizing in a web app – just suffix "| npx logscreen"

#36

Earlier quoted context omitted.

> All you need to know. For those of us not in the know, what does that mean?

> For those of us not in the know, what does that mean? I reckon that some people are either critical of LLMs due to the data that they're trained on (concerns about the legality of using the outputs, or the ethics of taking open source projects with a variety of licenses and how transformative or not the output might be), or question the quality of the code that they might output. Oh, also there's hype cycles and ri…

In that case, I'd quote the guidelines to GGP poster:

> Please don't fulminate. Please don't sneer, including at the rest of the community.

https://news.ycombinator.com/newsguidelines.html

Re: Show HN: Piping logs, visualizing in a web app – just suffix "| npx logscreen"

#37
post #20

Earlier quoted context omitted.

I think this is more designed for streamed output rather than viewing files. Vim doesn't seem to support that, in fact it just says "Vim: Reading from stdin..." forever.

Hmm.. I guess you could write a little script (2 lines?), let's call it "vimlive" which reads from stdin, streams to a temp file and opens that temp file in vim. Then with: command | vimlive You get vim with the current state of the data and you can update it with :e

You can have vim constantly refresh a buffer if it's modified externally, like this turns your buffer into a kinda-sorta-version of `tail -f`:

    :set autoread | au CursorHold * checktime | call feedkeys("G")
So if it's already a file, just open it with vim; if it's a STDOUT/STDERR stream, redirect/`tee` to a file and open that.

Re: Show HN: Piping logs, visualizing in a web app – just suffix "| npx logscreen"

#38

Congrats on launching! Its interesting to see that ChatGPT is able to build something I've been working on ( https://logdy.dev ) for last two months. I guess new era is around the corner then.

Your landing page looks fantastic, just wanted to throw that out (before ChatGPT starts making that, too)

Re: Show HN: Piping logs, visualizing in a web app – just suffix "| npx logscreen"

#39
This is handy stuff, thanks for sharing. We are working on transporting tasks back and forth from TUIWebAppVR ; this is a great and straightforward example of that.

I use VSCode CoPilot constantly as simple augmentation and typing-saving — not for wholesale creation of code. I’ve seen my pre-novice daughter use ChatGPT and the results were mixed (good in some ways, horrible in others).

Can you elaborate more on your ChatGPT/LLM working style for this?

Re: Show HN: Piping logs, visualizing in a web app – just suffix "| npx logscreen"

#40

Congrats on launching! Its interesting to see that ChatGPT is able to build something I've been working on ( https://logdy.dev ) for last two months. I guess new era is around the corner then.

I was looking for something like this for a while, and it could be just the landing page, but I much prefer a tool that's been built slowly with thought and consideration (which is evident from your landing page).

How does your tool handle semi-permanent usage or very long logs? For instance, I would run this to view logs from an ssh server that's been up for 6 months, when systemd has rotated the log file etc.

Post reply on HN