[BUG] Missing RDS metrics about yet-another-cloudwatch-exporter HOT 2 CLOSED

@jdavid5815 thanks for the detailed bug report.

I don't see any particular issue with the config you pasted (although would be better to add formatting to your ticket for easier readability). In any case, you can find and example RDS config at https://github.com/nerdswords/yet-another-cloudwatch-exporter/blob/master/examples/rds.yml

I think it might be good to try to temporarily simplify your config while we debug the issue. Could you please change it to have only two metrics, one that you think it's working correctly and one that is not working as expected. Then could you please post any log message from the container? (running yace with -debug would be great)

from yet-another-cloudwatch-exporter.

Okay, so I simplified the config to:

apiVersion: v1alpha1
discovery:
  jobs:
  - type: AWS/RDS
    regions:
      - eu-west-1
    searchTags:
      - key: prometheus
        value: true
    metrics:
      - name: CPUUtilization
        statistics:
          - Average
        period: 300
        length: 10800
      - name: ReadIOPS
        statistics:
          - Average
        period: 60
        length: 10800

As requested, I now have one metric that works, which is CPUUtilization and one which doesn't: ReadIOPS

I was just about to post the whole debug file, but there was really nothing special to see.. so I opened the AWS console and checked the CloudWatch logs themselves .. the metrics I wanted are not there!

What I didn't take into account was that fact that all databases were of the serverless type... Apparently, metrics are different for Aurora database:

Aurora Metrics

So it turns out, YACE is working as designed. However, I would like to change this BUG report into a feature request:

scrape Aurora metrics.

Shall I log a separate ticket?

Sorry for the inconvenience.

from yet-another-cloudwatch-exporter.