Increase Cloud SQL alert threshold to 98% #569
Merged
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
Signed-off-by: Cody Soyland <codysoyland@github.com>
codysoyland
force-pushed
the
disk-utilization-alert-tuning
branch
from
df74644
to
99ec09e
Compare
Signed-off-by: Cody Soyland <codysoyland@github.com>
bobcallaway
approved these changes
Mar 9, 2023
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.
As autoresize is enabled, the Cloud SQL disk utilization is always roughly ~91-95%. This caused a few alerts as the disk utilization hit the 95% threshold a few times prior to disk autoresize. Increasing to 98% should be safe and avoid unneccesary alerts. Typical rate of growth is currently around 1%/day, so in the event of autoresize failure, we will still have >24h to remedy a situation where we hit 98% capacity.