[marmaduke]

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.

[piterrro]

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.

[emadda]

Why would you watch logs for more than 6 months?

Do you filter them? What does the system you are watching do?

[marmaduke]

for instance, running a nextcloud instance through docker compose, I'd like to have a lightweight web ui for browsing the server logs. not just for 15 minutes but for longer periods of time.

on an hpc cluster, I want to want logs from the slurmctld forever essentially without having to login and grep through the logs.

there's a bunch of online services for this, there's ELK stack, there's grep, and few things sit in between. hence my question

[piterrro]

then the problem is not viewing the logs but storing them, maybe compressing, and then retrieving. If that's not a problem (size) then with some cron magic you should be able to store the logs from specific locations into a single one so rotation doesn't eat them and then just view using a log viewer of your choice.