-
-
Notifications
You must be signed in to change notification settings - Fork 387
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Is there an existing issue for this?
- I have searched the existing issues
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.
vniche-swisscom, artemkulishsigma, yoshiakiley and Jozefiel
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working