Tom Graupner
Tom Graupner
While testing AWS CloudWatch Container Insights with Enhanced Observability I felt the urge to provide a configuration with a better fit to our needs. Reading through your guides, the section...
While reading the best practices guides I came across this line stating: > Metrics collected by Container Insights are charged as custom metrics. --- ### Permalinks: https://github.com/aws-observability/observability-best-practices/blob/97774e64728c09fc85fb37b1f618af8d722915cb/docs/en/guides/containers/aws-native/ecs/best-practices-metrics-collection-1.md?plain=1#L29 https://github.com/aws-observability/observability-best-practices/blob/97774e64728c09fc85fb37b1f618af8d722915cb/docs/en/guides/containers/aws-native/eks/amazon-cloudwatch-container-insights.md?plain=1#L15 --- However,...
Currently, this test is always executed with one specific user. Hence, it can run into API limits of the Google Reset Password API
The redirect validated in this tests depends on the ownership of the clicked entry. We need to split this into two tests and we need to find a way to...
**Describe the bug** The EKS add-on documentation on the official AWS page is linking to this Getting Started Guide: https://aws-otel.github.io/docs/getting-started/adot-eks-add-on When following this guide, no metrics are send to CloudWatch...