cloudwatch_exporter icon indicating copy to clipboard operation
cloudwatch_exporter copied to clipboard

[bug]: Unable to access AWS/RDS BurstBalance metrics

Open r3kzi opened this issue 2 years ago • 2 comments

What did you do

region: eu-central-1
warn_on_empty_list_dimensions: true
metrics:
- aws_namespace: AWS/RDS
  aws_metric_name: BurstBalance
  aws_dimensions:
    - DBInstanceIdentifier
$ aws cloudwatch list-metrics --metric-name BurstBalance --namespace AWS/RDS | jq ".Metrics[].Dimensions"

What did you expect to see?

BurstBalance metrics in the same way like e.g. DatabaseConnections are exposed.

This works:

region: eu-central-1
warn_on_empty_list_dimensions: true
metrics:
- aws_namespace: AWS/RDS
  aws_metric_name: DatabaseConnections
  aws_dimensions:
    - DBInstanceIdentifier

What did you see instead? Under which circumstances?

$ docker run -p 9106:9106 -v $(pwd)/config.yml:/config/config.yml prom/cloudwatch-exporter
[....]
Dec 27, 2022 2:44:34 PM io.prometheus.cloudwatch.DefaultDimensionSource listDimensions
WARNING: (listDimensions) ignoring metric AWS/RDS:BurstBalance due to dimensions mismatch

Environment

  • Exporter version:
$ curl -Ss http://localhost:9106/metrics  | grep cloudwatch_exporter_build_info       
cloudwatch_exporter_build_info{build_version="0.15.1",release_date="2022-10-25",} 1.0
  • Operating system & architecture: Linux x86_64 / Ubuntu
  • Running in containers? y
  • Using the official image? y

I think it's caused by --recently-active.

When i run aws cloudwatch list-metrics --metric-name BurstBalance --namespace AWS/RDS --dimensions Name=DBInstanceIdentifier --recently-active PT3H it will return a empty Metrics list.

Without --recently-active it works.

r3kzi avatar Dec 27 '22 14:12 r3kzi