tl/dr; I would love to have the application logs, one can already access via the UI, stored permamently.

Context: log aggregation is quite expensive / complex by itself. There is stuff like splunk that is mainly focused on big enterprise. The logs ploi provides are already like 95% of what I need anyway, so using an external aggregator seems like a out of proportion thing to do. On the other hand, logs are only accessible as long as the containers live. But for some cases it might be really good to have historical logs:

  1. You notice you have been attacked like a week ago and want to gather as much intel as possible
  2. You have cron jobs that produce logs which show wether or not they did run and how long/etc

Proposal: Make it possible to store the logs of a container on your own managed s3. Maybe something like /logs/2026-03-17/container-id.log. I do not need it to be realtime. The realtime-aspect is well covered in the UI already. But that way I would have the peace of mind that I could download and grep stuff if I needed to after the fact.

Further thoughts: This is a quite uncommon approach to this problem, I guess. But as I am happy to not have the struggle of managing my own VPCs and Deploymentpipelines, you as a PaaS are also in a unique position of providing further quality of life features, that would be achieved differently in classical approaches.

· · Edited
·

@zander just built this, I've tested it, works really well. It allows logging to your external storage, every 5 minutes. I will also be looking into adding a new tab inside that logs tab, that allows to read the logs straight from your bucket in the panel, saves a bit more hassle. That's for a future update.

1 total vote

Long term log persistance

2 total votes
Quick Actions
Activity
View recent activity and updates
Use arrow keys to navigate