Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

github.com

Post reply on HN
Print view View original

61–70 of 81 posts

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

#61

Post by piterrro »

corytheboyd wrote: post #44
piterrro wrote: post #25

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.

Please keep working on this! I started a similar tool because I desperately needed it, but haven’t found the time to maintain it. https://github.com/corytheboyd-smartsheet/json-log-explorer Having something like the log explorer in DataDog for local development is so insanely useful

That was the idea exactly: I wanted to have DD log explorer locally that works insanely fast to be coupled within development process. As much as I love terminal, its just so limiting when it comes to browsing and filtering through more content.

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

#62

Post by piterrro »

mittermayr wrote: post #38
piterrro wrote: post #25

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)

Thanks!

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

#64

Post by jasonjmcghee »

soorajsanker wrote: post #11
jasonjmcghee wrote: post #4

Earlier quoted context omitted.

I was going to ask about the strange combination of package.json and inlined cdn js dependencies (especially strange because it's a local server) Suppose that answers it.

Haha yeah, I wanted to frame this as a single file tool, and hence all the quick wins. But later moved the react app into a separate file because I was not getting the syntax highlights and all. Definitely this can be made better with proper packaging and tooling! As I mentioned, more than the idea, implementation was an experiment on the ability of collaborative iterations with GPTs- it was fun!

Oh- how much manual intervention was there? It was not entirely generated?

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

#65

Post by soorajsanker »

psim1 wrote: post #57

This is a solution looking for a problem. The browser is a horrible place for viewing text logs. Companies like Splunk and Datadog put countless hours into trying to make it work and it's never not-painful to view logs in a browser.

What are the main specific issues that you felt difficult in viewing logs on a browser? imagine there is better visualisation, parsing, highlighting, filtering, collapse etc.? I feel like the terminal is where I spend more time looking for the relevant parts from the logs.

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

#66

Post by piterrro »

marmaduke wrote: post #40
piterrro wrote: post #25

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.

Thanks for your kind words. I have a feature onnthe roadmap which is very close to delivery that will allow you to load a big log file and browse it through the UI. As long as you can load the content from disk or remotely, Logdy will be able to handle that. The aim isnto provide DataDog like experience but in a portable and temporary way, that allows you to set it up quickly, check what you need, tear down and move on. All without much hassle or costs for sending the logs to a remote service.

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

#67

Post by soorajsanker »

kevincox wrote: post #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)

Are you talking about the difference between 0.0.0.0 and 127.0.0.1 /localhost (loopback address)? If so It should be a tiny thing to change to implement I can add that on the next update- I just went with the express JS defaults to keep things simple:)

Or I can even make a flag to configure this :thinking

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

#68

Post by ggpsv »

soorajsanker wrote: post #67
kevincox wrote: post #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)

Are you talking about the difference between 0.0.0.0 and 127.0.0.1 /localhost (loopback address)? If so It should be a tiny thing to change to implement I can add that on the next update- I just went with the express JS defaults to keep things simple:) Or I can even make a flag to configure this :thinking

`app.listen` uses the same signature as Node's `server.listen`. You can specify the `host` [0] or else it defaults to `0.0.0.0`. This means that when you run this service, it will be accessible to anyone that can reach the server.

Typically, services allow you set the host address by configuration. This way you can set it to `127.0.0.1` so that it is only available locally.

[0]: https://nodejs.org/api/net.html#serverlistenport-host-backlo...

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

#69

Post by gothink »

soorajsanker wrote: post #67
kevincox wrote: post #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)

Are you talking about the difference between 0.0.0.0 and 127.0.0.1 /localhost (loopback address)? If so It should be a tiny thing to change to implement I can add that on the next update- I just went with the express JS defaults to keep things simple:) Or I can even make a flag to configure this :thinking

If you do make it configurable, it's still a good idea to make the default `127.0.0.1` for the reasons @ggpsv mentioned. Since the link automatically opens at `http://localhost:PORT` anyway, it's an easy security win.

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

#70

Post by dloss »

psim1 wrote: post #57

This is a solution looking for a problem. The browser is a horrible place for viewing text logs. Companies like Splunk and Datadog put countless hours into trying to make it work and it's never not-painful to view logs in a browser.

Some CLI viewers for logs are listed on https://github.com/dloss/klp, as alternatives to my own little tool "klp".
Post reply on HN