fix(agent): report MongoDB wire message lengths - #11914
Closed
jiangjiang248 wants to merge 1 commit into
Closed
jiangjiang248 wants to merge 1 commit into
jiangjiang248 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.
This PR is for:
Fixes MongoDB request and response lengths being reported as zero
Steps to reproduce the bug
agent/resources/test/flow_generator/mongo/.MongoDBInfo:req_lenandresp_lenremain zero even though the MongoDB message header contains a nonzero length (for example, 230 bytes for the request and 285 bytes for the response inmongo-msg.pcap).Changes to fix the bug
MongoDBInforeturned byparse_payload, instead of the parser's internalself.info.Affected branches
Checklist
rustfmt --edition 2021 --check agent/src/flow_generator/protocol_logs/sql/mongo.rs