Monitoring rds service delay is too large.

[jeffaryhe]

Is there an existing issue for this?

• I have searched the existing issues

YACE version

v0.61.2

Config file

apiVersion: v1alpha1
discovery:
jobs:
- type: AWS/RDS
regions:
- ca-central-1
period: 60
length: 120
metrics:
- name: EngineUptime
statistics: [Maximum]
- name: CPUUtilization
statistics: [Average]

Current Behavior

I tested the minimum rds cpu time that can be obtained here, which caused the data delay to be too large and unable to accurately monitor alarms. Delay for at least 3 minutes to reflect the accurate alarm value.

Expected Behavior

Can obtain monitoring indicators within 60 seconds

Steps To Reproduce

no

Anything else?

No response

[tyagian]

I suggest you to fix the period and length time. Its good to keep them same.

The period parameter in your YACE config is set to 60, meaning it fetches CloudWatch metrics at 1-minute intervals. However, the length parameter is set to 120, which means YACE fetches data from the last 2 minutes. This can cause YACE to pull older data, resulting in delays.