Vladyslav Miletskyi
Vladyslav Miletskyi
v2.3.0 still has high CPU usage
@lacer-utkarsh https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Agent-PrometheusEC2.html > The IAM role for the EC2 instance where the CloudWatch agent runs must include the ec2:DescribeInstance permission. For example, you could attach the managed policy AmazonEC2ReadOnlyAccess to...
Scrape EC2s, which are tagged with `prometheus.io/scrape=true` ```yaml inlineScrapeConfig: | - job_name: ec2 honor_labels: true ec2_sd_configs: - region: us-west-1 filters: - name: tag:prometheus.io/scrape values: - "true" relabel_configs: - source_labels: [__meta_ec2_tag_prometheus_io_path]...
fixes #2571
Hello @pof-jhansilva You can try running workflow like [this](https://github.com/docker/setup-buildx-action): ```yaml - name: Set up QEMU uses: docker/setup-qemu-action@v3 - name: Set up Docker Buildx uses: docker/setup-buildx-action@v3 - name: Build and push...
Upgraded to `1.102.1-cluster` as per requests. I also restarted the agent afterward. No changes.
confirming on 0.32 as well