search

prometheus-community / yet-another-cloudwatch-exporter

Prometheus exporter for AWS CloudWatch - Discovers services through AWS tags, gets CloudWatch metrics data and provides them as Prometheus metrics with AWS tags as labels
Apache License 2.0
983 stars 335 forks source link

[BUG] AWS/AmazonMQ always returning No metrics data found #1552

Open danielbargas opened 2 weeks ago

danielbargas commented 2 weeks ago

Is there an existing issue for this?

YACE version

v0.61.2

Config file

apiVersion: v1alpha1
sts-region: redacted
discovery:
  jobs:
    - type: AWS/AmazonMQ
      regions:
        - redacted
      roles:
        - roleArn: "redacted"
      period: 300
      length: 3600
      metrics:
        - name: NetworkOut
          statistics: [Minimum, Maximum, Average]
        - name: NetworkIn
          statistics: [Minimum, Maximum, Average]
        - name: QueueSize
          statistics: [Minimum, Maximum, Average]
        - name: ConsumerCount
          statistics: [Minimum, Maximum, Average]
        - name: ProducerCount
          statistics: [Minimum, Maximum, Average]
        - name: EnqueueCount
          statistics: [Minimum, Maximum, Average]
        - name: DequeueCount
          statistics: [Minimum, Maximum, Average]
        - name: MemoryUsage
          statistics: [Minimum, Maximum, Average]
        - name: CpuUtilization
          statistics: [Minimum, Maximum, Average]
          ## Test other metrics
        - name: AckRate
          statistics: [Minimum, Maximum, Average]
        - name: SystemCpuUtilization
          statistics: [Minimum, Maximum, Average]

Current Behavior

For our RabbitMQ brokers, YACE always outputs the following for the AWS/AmazonMQ namespace

"job_type":"AWS/AmazonMQ","level":"info","msg":"No metrics data found"

Expected Behavior

I would expect YACE to find some or all the above metrics

Steps To Reproduce

Deploy MQ config Check YACE log/stdout

Anything else?

YACE does work fine for us for other namespaces like RDS or Backup using the same AWS IAM role. I woudl expect the error to be different anyway if it was a permissions thing.