v12 - fix(rule-flood-guard): notify only the affected tenant, without namin… - #2496
Merged
yllada merged 1 commit intoAug 20, 2026
Merged
Conversation
…g it The flood notification went to the tenant whose rule was disabled and also to the platform tenant, so the operator would keep the instance-wide visibility they had before the disable became per-tenant. In an MSSP that turns every flood in every tenant into a ping on the operator's bell, which is the same alert fatigue this plugin exists to prevent. The tenant is the one who can act on it, so the copy is gone. With no operator copy left, naming the tenant in the message was noise: the only reader is the affected tenant, and showing them their own UUID tells them nothing. The message now speaks to them directly. The tenant is still in the structured log, which is where operators read from.
✅ AI review — CleanNo issues detected in this diff. ✅
|
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
1 participant
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.
The flood notification also went to the platform tenant, so the operator would
keep the visibility they had before the disable became per-tenant. In an MSSP
that means every flood in every tenant pings the operator — the same alert
fatigue this plugin exists to prevent. Only the affected tenant is notified now.