You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a regional Aurora MySQL cluster of two. 1 reader instance and 1 writer instance.
Number of aws_rds_cpuutilization_maximum{} metrics is bigger than the number of instances.
Expected Behavior
dimension_DatabaseClass label to be present on all metrics.
Why is it listed only on the last two metrics that don't identify RDS at all?
Same thing with aws_rds_freeable_memory_average{} . Memory size depends on instance size. So, we have recorded a metric like aws_rds_memory_max_alloc{} based on AWS documentation. For example:
We could join both metrics on dimension_DatabaseClass label to make threshold dynamic, but we cannot do that.
Steps To Reproduce
Deploy yace with my config and try to pull RDS cloudwatch metrics.
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
YACE version
master-baf1c3f
Config file
Current Behavior
We have a regional Aurora MySQL cluster of two. 1 reader instance and 1 writer instance.
Number of aws_rds_cpuutilization_maximum{} metrics is bigger than the number of instances.
Expected Behavior
dimension_DatabaseClass
label to be present on all metrics.Why is it listed only on the last two metrics that don't identify RDS at all?
Same thing with aws_rds_freeable_memory_average{} . Memory size depends on instance size. So, we have recorded a metric like aws_rds_memory_max_alloc{} based on AWS documentation. For example:
We could join both metrics on dimension_DatabaseClass label to make threshold dynamic, but we cannot do that.
Steps To Reproduce
Deploy yace with my config and try to pull RDS cloudwatch metrics.
Anything else?
No response
The text was updated successfully, but these errors were encountered: