Skip to content
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

Open
mudler opened this issue Apr 11, 2024 · 3 comments
Open

feat: debugging logs #2462

mudler opened this issue Apr 11, 2024 · 3 comments
Labels
enhancement New feature or request question Further information is requested triage Add this label to issues that should be triaged and prioretized in the next planning call

Comments

@mudler
Copy link
Member

mudler commented Apr 11, 2024

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

@mudler mudler added enhancement New feature or request triage Add this label to issues that should be triaged and prioretized in the next planning call labels Apr 11, 2024
@jimmykarily
Copy link
Contributor

@ci-robbot
Copy link
Collaborator

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 ci-robbot added the question Further information is requested label Apr 24, 2024
@ci-robbot
Copy link
Collaborator

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request question Further information is requested triage Add this label to issues that should be triaged and prioretized in the next planning call
Projects
Status: Todo 🖊
Development

No branches or pull requests

3 participants