fix(proxy): filter requests with empty messages from database storage #165
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
MetricsService.storeRequest()to skip storage whenmessageCount === 0Context
Even after recent fixes for empty Bedrock responses and internal operations, two types of "empty" requests were still being stored:
messagesarray is emptyBoth of these pollute the database with non-meaningful request data.
Changes
messageCount === 0inputTokens === 0 AND outputTokens === 0 AND content.length === 0Test plan
🤖 Generated with Claude Code