1 Answer
- Newest
- Most votes
- Most comments
0
Thank you so much. I fixed the error in the file: https://raw.githubusercontent.com/aws-samples/amazon-cloudwatch-container-insights/latest/k8s-deployment-manifest-templates/deployment-mode/service/cwagent-prometheus/prometheus-eks-fargate.yaml It somehow misplaced these lines: kind: ConfigMap metadata: name: prometheus-config namespace: amazon-cloudwatch
answered a year ago
Relevant content
- asked 6 months ago
- asked a year ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 2 years ago
I do understand that you had added the shared scrape config to configmap and running in to Parsing error. Since this error points to incorrect YAML formatting of the manifest, I believe the scrape config might have been added with wrong indentation or as the error message suggests there might be missing keys. Although it is hard for us to tell without having the complete YAML manifest that you are trying to apply. Please refer to this manifest(that I grabbed from the same link you were referring to - https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/ContainerInsights-Prometheus-Setup-configure.html) -- https://raw.githubusercontent.com/aws-samples/amazon-cloudwatch-container-insights/latest/k8s-deployment-manifest-templates/deployment-mode/service/cwagent-prometheus/prometheus-eks.yaml
Please ensure that your shared scrape config is placed under the below snippet as shown below:
apiVersion: v1 kind: ConfigMap metadata: name: prometheus-config namespace: amazon-cloudwatch data:
prometheus config
prometheus.yaml: | global: scrape_interval: 1m scrape_timeout: 10s scrape_configs: ====== Here comes the scrape Config=== ======== ======== ======== ======== ========
Considering that we need additional information to be able to completely address the issue, I would suggest that you raise a support ticket with AWS Premium Support to get assistance with this issue.