Repository navigation
fix(ai): preserve alert rule instance scope - #7341
Open
X-LightYear wants to merge 1 commit into
Open
X-LightYear wants to merge 1 commit into
X-LightYear wants to merge 1 commit into
Conversation
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.
Summary
instanceIdwhen projecting alert rules forrmq.alert.rule.listRoot cause
AlertRuleListItem.from(AlertRuleVO)droppedAlertRuleVO.instanceId. The tool lists rules across the whole Studio deployment, so the serialized result could not identify the Instance to which a rule was bound.Fix
Copy the optional instance binding into the MCP projection and document it in the catalog. Global rules continue to omit the field through the existing non-null serialization policy.
Testing
instanceIdwas absentAlertRuleListToolHandlerTest: passedToolOutputSchemaContractTest: passedgit diff --check: passedFixes #7340