Fixed an error where the service request to get all faults with include_muted=false also returned the muted faults.#414
Merged
bburda merged 1 commit intoJun 10, 2026
Conversation
…de_muted=false also returned the muted faults.
bburda
approved these changes
Jun 10, 2026
bburda
left a comment
Collaborator
There was a problem hiding this comment.
Thanks for the fix @evTessellate, root cause is spot on. Merging.
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.
Pull Request
Summary
The gateway returns a list of muted faults even when the service request ask to exclude them. It caused the web UI and Foxglove to display muted faults even if muting correlation rules where defined.
Issue
Link the related issue (required):
Type
Testing
How was this tested / how should reviewers verify it?
As described in the #413 issue, I created a small setup with a
MAIN_FAULTand aCASCADED_FAULTwhere the former should mute the later based on a hierarchical correlation_rule. The same setup was used to resolve the problem. I used the Foxglove plugin to validate that with the changes theCASCADED_FAULTdidn't appear in the UI. Alsocurl "http://localhost:8080/api/v1/faults?include_muted=false"now excludes the muted faults while `curl "http://localhost:8080/api/v1/faults?include_muted=true" keeps it.Checklist