feat: debugging logs

[mudler]

Is your feature request related to a problem? Please describe. Debugging issues without logs or pointers can be troublesome

Describe the solution you'd like An option via cmdline and/or cloud config file to enable "dumping all the logs" (app level, for instance zerolog) to an endpoint that can be used later on to parse the logs (maybe integrated with an existing tool):

• systemd
• golang stacktrace (and pointer to code section, also to display in logs https://github.com/rs/zerolog?tab=readme-ov-file#error-logging-with-stacktrace )
• kairos-agent
• immucore

Acceptance criteria

• [ ] A new subcommand in the agent collects all availble logs (manual use) and puts them in an archive that can be used for submitting e.g. issues
• [ ] The kairos agent reads a cloud config or a cmdline, and if present a specific sentinel it will dump all logs to the specified location (can be an API endpoint, or just a mountpoint)

Describe alternatives you've considered N/A

Additional context

Idea In conversation with @jimmykarily

[jimmykarily]

https://trunc.org/learning/syslog-daemons-difference

[ci-robbot]

Hello! I'm a bot, an experiment of @mudler and @jimmykarily. Thank you for opening this issue, and we appreciate your suggestion.

Please, could you provide more information on how to reproduce the issue and the versions of the relevant artifacts that you are using (such as the version of the Kairos app, the Kairos-agent, and any other components)? This would help us better understand the context and troubleshoot any potential issues.

Also, it would be helpful if you could expand on the 'Additional context' section, specifically on the 'Idea In conversation with @jimmykarily' part.

Please add more details as it would help the community and the maintainers to understand the issue better and ensure it's not missed.

Current labels: [enhancement triage]

[ci-robbot]

Hello! I'm a bot, an experiment of @mudler and @jimmykarily. I just added the 'question' label to your issue #2462 because some required information is missing. In order to better assist you, please provide:

• A clear description of the issue or feature you'd like to request in the "Debugging logs" feature,* Steps to reproduce the issue if it's a bug (if not, you can skip this step),* The versions of the relevant artifacts being used (e.g. CLI version, cloud config version, operating system, etc.). Thanks for your understanding and cooperation!