[fix] validate the metric history query inputs - #4274
Open
Duansg wants to merge 2 commits into
Open
Conversation
zqr10159
approved these changes
Jul 30, 2026
zqr10159
left a comment
Member
There was a problem hiding this comment.
Reviewed against the 1.9.0 pre-release metric-history injection findings. Service-layer allowlists cover range, identifiers, and instance values before any storage query is built. The focused local suite passes (7 tests) and CI is green.
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.
What's changed?
Validate the time range and identifier format of metric history queries in the service layer, covering every storage implementation.
Checklist
Add or update API