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