Feature Request: Show logs of older instances

[flobaader]

Logs are essential for understanding and managing IT systems, especially in Kubernetes-based PaaS environments. They help in troubleshooting, monitoring performance, and ensuring security. Improving log management in our Kubernetes-based PaaS will greatly enhance our ability to analyze and utilize these important data sources.

Idea: Store logs of older instances for a few days

• Extended Log Retention: Store logs for at least 7 days for in-depth analysis and troubleshooting.
• Access to Older Instance Logs: Enable retrieval of logs from both current and terminated instances.
• Search and Filter Tools: Implement advanced search and filtering for easy navigation and analysis of logs.
• User-Friendly Interface and API: Provide a simple interface and API for accessing and managing logs.
• Performance Optimization: Ensure extended log storage does not significantly impact system performance.

[blacksails]

Instead of implementing a log store we could also consider wether we should provide integration points towards dedicated logging systems like splunk, humio, loki and the cloud provider specific logging systems.

There is a few downsides to implementing this at our current stage

• Logs can potentially take up a lot of space, which might cause problems with regards to the database
• If rig stores logs, indepth risk assesments will be required in some companies (feature should be able to be disabled)
• Providing an exceptional log experience is not a simple task (This is why some companies solely focus on this)

IMO, we should icebox this for now. @andersjohnsen