Open v1ctorrhs opened 3 years ago
It's because all possible dimensions are discovered after https://github.com/ivx/yet-another-cloudwatch-exporter/pull/315
You can revert to v0.25.0-alpha
and use:
- type: rds
regions:
- us-east-1
searchTags:
- key: environment
value: test
awsDimensions: [DBInstanceIdentifier]
metrics:
- name: NetworkReceiveThroughput
statistics:
- Average
period: 300
length: 3600
Can we add old behaviour as a feature? Searching or making graphs through different sets of labels for the same metric become much trickier. With that behaviour you also have to make aggregation through metric more carefully to avoid duplicates.
Might be the same issue as #404
Hi guys,
I'm running v0.26.3-alpha inside an EKS cluster.
Authentication is handled using a service account that has an IAM role attached to it.
I'm running the following yace-exporter configuration for a single RDS Postgresql instance and I keep getting the same metric multiple times with different labels.
Adding another metric results in the same behavior