[EKS] [Request]: Make API/ETCd/Rest logging in the performance log group configurable
- 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**
Similar to the Control Plane Logs config section

in the console create a Performance Logging config section
something like
Performance Logging
enable/disable API Server
enable/disable rest client
enable/disable etcd
enable/disable Pod
This would give greater control over costs for following log group
`/aws/containerinsights//performance`
API Server performance logs aren't really needed by default.
Pod CPU usage etc. though is useful by default.
**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?**
This maybe possible by configuring the AWS Observability Addon but I haven't as yet found out how to do so and having it exposed in a controlled way within the console and by implication also the API would be very beneficial.
**Are you currently working around this issue?**
No, have not found a workaround
Contributor guide
Research direction
Start by reviewing the existing Control Plane Logs configuration in the EKS console and API, then check whether the AWS Observability Addon exposes equivalent settings. Define how API Server, REST client, etcd, and Pod performance logging map to the /aws/containerinsights//performance log group, and verify that the console and API provide consistent cost controls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100