patch: prevent nosql injection for metric resources #578
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.



This pull request improves the handling and validation of query parameters for metric-related API endpoints and enhances input sanitization before querying the database. The main changes include stricter validation of request parameters, improved type handling, and the introduction of input formatting to prevent inconsistent or unsafe values.
API request validation improvements:
/metric/data/and/metric/statistics/endpoints, including type checks and length constraints forkey,environment,component, andgroup, as well as ISO8601 validation for date filters. [1] [2]pageparameter by converting it to aNumberand checking forNaNusingNumber.isNaN.Input sanitization and consistency:
formatInputhelper inbuildMetricsFilterto sanitize and normalize theenvironment,component, andgroupquery parameters before using them in database queries, reducing the risk of inconsistent or unsafe values. [1] [2]resultquery parameter is explicitly converted to a boolean value before use.