Kaushik Surya
Kaushik Surya
Have we considered attaching an [expiration policy](https://docs.aws.amazon.com/systems-manager/latest/userguide/parameter-store-policies.html) at the time of creation? That way we dont have the throttling issue and dont need to manage cleanup ourselves.
Going to look into this during KubeCon Contribfest
To provide the flexibility around the volume of logs emitted, we do now support allowing customization of the FluentBit config via the add-on advanced config. Please see https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/install-CloudWatch-Observability-EKS-addon.html#CloudWatch-Observability-EKS-addon-CustomFluentBit for further...
Hello, The recent versions of the `amazon-cloudwatch-observability` EKS add-on should only pull from private ECR registries as outlined here: https://docs.aws.amazon.com/eks/latest/userguide/add-ons-images.html Please try updating to the latest version of the add-on...
Starting with `v3.0.0-eksbuild.1` of the add-on, there is a new advanced config option, `agents`, which can be used to manage 0 or more CloudWatchAgent installations. The default is still the...
This is now available as part of [v3.7.0](https://github.com/aws-observability/helm-charts/releases/tag/amazon-cloudwatch-observability-3.7.0) of the EKS add-on and helm-chart. In addition to nodeSelector, component level overrides can also be specified for affinity, tolerations and updateStrategy....
Starting with `v3.0.0-eksbuild.1` of the add-on, the `priorityClassName` is set to `system-node-critical` by default for both the cloudwatch-agent and the fluent-bit daemonsets. Advanced config provides an option to specify a...
Please re-open if you require further assistance.
Could you also please provide us with a sanitized snapshot of your raw prometheus metrics so we can try to reproduce the issue?