Anuj Tyagi

@scholzj Do we have fixed it yet or estimate which version should have fix of this?

If I use https in destination registry url then I don't get 401 error but this error. ``` $./helm_image_mirror.sh -c config.yaml WARNING: The requested image's platform (linux/amd64) does not match...

@frederiksf I also observed same bug. Do we need both histogram and float type queries for this? Any workaround to disable histogram type rules?

Fixed and working as expected.

I have removed enableMetricData: true and now I see error after upgrading version v0.50.0 ``` {"account":"xxx","arn":"","error":"expected to discover resources but none were found","job_type":"lambda","level":"error","msg":"No tagged resources made it through filtering","region":"us-west-1","time":"2023-04-11T21:43:46Z"} 2...

I have 2 queries: - If there are no lambda functions in above regions, will it throw this error? Can I stop it from flooding the logger. So, since it...

@cristiangreco The issue happen in case of Lambda @edge functions. Since it use CloudFront and thus Lambda metrics are available in different regions based on from where traffic is coming....

Sure. May I know where do we have option in yace helm chart to enable debug mode: https://github.com/nerdswords/helm-charts/blob/main/charts/yet-another-cloudwatch-exporter/values.yaml ?

Okay, I will try to test in Lab. Meanwhile I also found similar another issue in past asked same query to collect metrics from different regions of edge lambda function...

@cristiangreco The workaround is to use lambda@edge as static job instead of discovery job. I have added PR to add in example how I fixed it but I recall it...