Skip to content

ROX-30068: disable memory utilization alerts for scanner-db#318

Merged
johannes94 merged 1 commit into
masterfrom
jmalsam/disable-scanner-db-memory-alerting
Jul 11, 2025
Merged

ROX-30068: disable memory utilization alerts for scanner-db#318
johannes94 merged 1 commit into
masterfrom
jmalsam/disable-scanner-db-memory-alerting

Conversation

@johannes94
Copy link
Copy Markdown
Contributor

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.

@johannes94 johannes94 requested a review from a team as a code owner July 11, 2025 06:57
@johannes94 johannes94 requested review from ludydoo and removed request for a team July 11, 2025 06:57
Copy link
Copy Markdown
Contributor

@ludydoo ludydoo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will that disable alerts for scanner-v4-db ?

@johannes94
Copy link
Copy Markdown
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.

@johannes94 johannes94 merged commit 56a7ad7 into master Jul 11, 2025
1 check passed
@johannes94 johannes94 deleted the jmalsam/disable-scanner-db-memory-alerting branch July 11, 2025 09:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants