Matthias Rampke

I believe we can change the metric names without waiting for the underlying implementation to change. It will be a long time until we can only support versions that have...

Yes, that's a great idea!

What should the default be? Preserve the current behavior, or can we settle on a reasonable default?

The reason is a change in the library, but this has been discussed in various places and the result of these was that it is correct not to accept inconsistent...

@beorn7 is there an FAQ entry or something for this?

This might be fallout from the AWS SDK v2 update. As a workaround, it does it work to supply a [configuration file](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-role.html) and make the exporter use it [via environment...

Hmm, since this is an upstream API limitation, it seems that filtering client-side would be useful but potentially costly as you would have to request _all_ metrics. I am confused...

I am also not sure how the exporter could _do_ this. The tag selection works by 1. [Getting resource IDs](https://github.com/prometheus/cloudwatch_exporter/blob/078674752ff7813819777eebc272d4aa2e4ae36b/src/main/java/io/prometheus/cloudwatch/CloudWatchCollector.java#L628-L630) from the resource tagging API 2. [Filtering a metric dimension...

The exporter isn't using boto3, it is using the Java SDK, although AFAIK both are basically generated clients so they inherit the upstream limitations. This pointed me in the right...

I updated the issue title and description