[HN Gopher] Show HN: Logdy.dev - web based log viewer UI for loc...
___________________________________________________________________
Show HN: Logdy.dev - web based log viewer UI for local development
environments
Author : piterrro
Score : 35 points
Date : 2024-02-06 17:11 UTC (5 hours ago)
(HTM) web link (logdy.dev)
(TXT) w3m dump (logdy.dev)
| pmig wrote:
| Nice project, I really like the idea. Is it possible to create
| multiple log streams at once?
| piterrro wrote:
| I'm working on it as we speak! My plan is to listen on multiple
| ports then attach the "origin" field to each log message with
| the port number it was produced with. This way you should be
| able to do:
|
| $ logdy socket 8001,8002,8003
|
| $ node app1.js | nc 8001;
|
| $ node app2.js | nc 8002;
|
| $ node app3.js | nc 8003;
|
| Wdyt?
| pmig wrote:
| Makes sense! I like the approach.
| zokier wrote:
| Not sure if you want to go that route, but unix sockets allow
| you to use SO_PASSCRED to get the pid of the connected
| process, you could use that as natural "origin" without
| requiring many ports
| piterrro wrote:
| Author here: Logdy is a self-hosted, single binary, open source
| cli tool that catches stdout from a terminal and sends it to web
| browser UI. It's goal is to structure the logs and save time
| searching and browsing them.
|
| This is an early version, I'm looking for feedback.
|
| If you would like to try the tool without downloading it visit:
| https://demo.logdy.dev/ Latest release:
| https://github.com/logdyhq/logdy-core/releases
| anirudhan wrote:
| This project might solve the problem I have been having for a
| long time but falls short. My usecase is that I have a directory
| with log files in multiple subdirectories. I would like to
| explore these logs by pointing logdy at this directory. Is this
| possible somehow?
| piterrro wrote:
| That depends on the constraints you have. Currently you can
| start a tail on multiple files if you don't need to distinguish
| the filenames in Logdy
|
| - $ logdy stdin 'tail -f file1.log file2.log' this use case is
| described here [1].
|
| Logdy currently works best with tailing, however exploring big
| files is not supported well as Logdy will stream the whole
| content if used like $ logdy stdin 'cat bigfile.log'. I'm
| planning to introduce another mode [2] that will work more like
| a 'less' command.
|
| [1] https://logdy.dev/docs/how-tos#how-to-tail-multiple-files
| [2] https://logdy.dev/docs/explanation/command-modes#read-soon
| zokier wrote:
| Have you considered getting logs from journal? That could make
| this useful also in ops context.
|
| License? Business model?
| piterrro wrote:
| You can
|
| $ logdy stdin 'journalctl -u service-name -f'
|
| I would need more feedback on a specific use case. I started
| with forwarding development logs in mind, however during the
| process I quickly realized there might be more use cases when
| one would find useful forwarding logs to web UI, example: ops,
| data science, long-running scripts. I hope to get feedback from
| these angles as well.
| iddan wrote:
| I've been waiting for something like this to pop up for a long
| while! Do you consider integrating with VSCode?
| piterrro wrote:
| That is my plan in the long term. I need to explore building
| VSCode extensions but that option is definitely on the table.
___________________________________________________________________
(page generated 2024-02-06 23:00 UTC)