use average for cpu utilization to aligns with AWS best practice #1674
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
yduartep
force-pushed
the
yduartep/change-rds-cpu-max-metric-to-average
branch
from
badce23 to
8eedde7
Compare
Signed-off-by: yduartep <[email protected]>
Signed-off-by: yduartep <[email protected]>
yduartep
force-pushed
the
yduartep/change-rds-cpu-max-metric-to-average
branch
from
4153b20 to
7a47fcb
Compare
cristiangreco
approved these changes
Apr 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Within the aws-rds dashboard which rolls with the AWS integration, the first panel (CPU utilization) uses the metric maximum to show utilization:
aws_rds_cpuutilization_maximumthis should use average
aws_rds_cpuutilization_averageThe justification for this is that average represents a sustained load, is less susceptible to spikes and generally aligns with AWS best practice in terms of auto scaling instances. Max generally should only be used for diagnosing specific issues with a machine. For that reason I think is is useful to have both.
The result will be something like this:
