[BUG] <title> Not able to scrape Metrics of all instances

[surapallykishore]

Is there an existing issue for this?

• [X] I have searched the existing issues

YACE version

0.60.0

Config file

config: |- apiVersion: v1alpha1 discovery: jobs:

• type: AWS/RDS regions: [ap-south-1] period: 300 length: 300 dimensionNameRequirements: [DBInstanceIdentifier] metrics:
  • name: CPUUtilization statistics: [Maximum]
  • name: DatabaseConnections statistics: [Sum]
  • name: FreeableMemory statistics: [Average]
  • name: FreeStorageSpace statistics: [Average]
  • name: ReadThroughput statistics: [Average]
  • name: WriteThroughput statistics: [Average]
  • name: ReadLatency statistics: [Maximum]
  • name: WriteLatency statistics: [Maximum]
  • name: ReadIOPS statistics: [Average]
  • name: WriteIOPS statistics: [Average]
• type: AWS/ElastiCache regions:
  • ap-south-1 period: 300 length: 300 metrics:
  • name: CPUUtilization statistics: [Average]

Current Behavior

Expected Behavior

Able to see metrics of only three RDS instances while I have a total of 17 rds instances in my AWS account

Steps To Reproduce

No response

Anything else?

No response

[surapallykishore]

Need Help @alext

[surapallykishore]

@cristiangreco hey could you please help me on this ?

[NickAdolf]

Do the other 14 instances have tags? In the same region? Are they running\producing metrics you see in the AWS Console?

[surapallykishore]

Hey @NickAdolf ,Yes and Yes they all are in the same region and I can the see metrics on console , but YACE is scraping metrics for 3 instances .

[surapallykishore]

Hey @NickAdolf , I was able to see all metrics when I was using prometheus exporter but it is making tooo many API calls so switched to YACE.