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.

Sign up for GitHub

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

Jump to bottom

Component-based logging for the CP #10230

Open
johnharris85 opened this issue May 14, 2024 · 3 comments
Open

Component-based logging for the CP #10230

johnharris85 opened this issue May 14, 2024 · 3 comments
Labels
kind/feature New feature triage/accepted The issue was reviewed and is complete enough to start working on it
Milestone
2.10.x

Comments

@johnharris85
Copy link
Contributor

Description

We should implement the ability to set different log levels per component, dynamically. This would bring Kuma more inline with how Envoy does logging and enable the triage of more complex issues with targeted log levels.
@johnharris85 johnharris85 added triage/pending This issue will be looked at on the next triage meeting kind/feature New feature labels May 14, 2024
@johnharris85 johnharris85 added this to the 2.8.x milestone May 14, 2024
@michaelbeaumont
Copy link
Contributor

@johnharris85 does this annotation qualify? Probably missing docs tbh..

@johnharris85
Copy link
Contributor Author

Sorry I didn't add much context. I mean for different internal components of Kuma. For example kds, k8s, plugins, policies, etc... Equivalent to Envoy's logging level per component, like dns, tls, hcm, etc..

@lahabana lahabana changed the title Component-based logging Component-based logging for the CP May 15, 2024
@lahabana lahabana mentioned this issue May 15, 2024
Closed
@jakubdyszkiewicz jakubdyszkiewicz added triage/accepted The issue was reviewed and is complete enough to start working on it and removed triage/pending This issue will be looked at on the next triage meeting labels May 20, 2024
@lahabana lahabana modified the milestones: 2.8.x, 2.9.x Jun 13, 2024
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Sep 12, 2024
@github-actions GitHub Actions
Copy link
Contributor

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@lahabana lahabana modified the milestones: 2.9.x, 2.10.x Sep 13, 2024
@slonka slonka removed the triage/stale Inactive for some time. It will be triaged again label Sep 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature New feature triage/accepted The issue was reviewed and is complete enough to start working on it
Projects
None yet
Milestone
2.10.x
Development

No branches or pull requests
5 participants
@lahabana @johnharris85 @michaelbeaumont @slonka @jakubdyszkiewicz