-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: debugging logs #2462
Comments
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] |
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:
|
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):
Describe alternatives you've considered
N/A
Additional context
Idea In conversation with @jimmykarily
The text was updated successfully, but these errors were encountered: