ROX-30068: disable memory utilization alerts for scanner-db#318
Merged
Conversation
ludydoo
reviewed
Jul 11, 2025
Contributor
ludydoo
left a comment
There was a problem hiding this comment.
Will that disable alerts for scanner-v4-db ?
Contributor
Author
|
@ludydoo Yes, IIRC the container is also called db. This was intentional. Because scanner-v4-db is also PSQL, if it is a metrics reporting issue with PSQL containers in general it would also affected scanner-v4-db in the same way. |
ludydoo
approved these changes
Jul 11, 2025
This file contains hidden or 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
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.
We're going to disable scanner-db high memory alerting, because we have metrics reporting issues.
See tickets and ticket comments for reasoning:
With this change we won't get alerted for high memory usage anymore, but we still have alerts for OOMs which will let us know if scaling is required.