[EKS] [Logging]: Ability to choose control plane log level (INFO, WARNING , ERROR)
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
**Tell us about your request**
Ability to set the log level for the control plane logs so that in some cases only Warning and Error logs can be streamed to CloudWatch. We can also consider the ability to choose a verbosity level such as (3,4,5, etc).
**Which service(s) is this request for?**
EKS
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Currently the log level of the control plane logs cannot be changed as it is a managed capability. Allowing to set the log level can help in streaming only certain types of logs (info, warning or error) to CloudWatch.
**Are you currently working around this issue?**
No workaround as of now.
Contributor guide
Research direction
The request concerns EKS control plane logs streamed to CloudWatch, but it names no repository files, tests, or implementation entry points. Start by reviewing the EKS logging controls and determine whether this roadmap issue has an actionable implementation path; done would mean supporting a selectable INFO, WARNING, or ERROR level.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100