[Packetbeat] Cherry-pick #11503 to 7.x: nfs: enforce unique ILLEGAL opname when failed to match operation #12025
Conversation
This file contains 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
…astic#11503) When we fail to map packet to a valid NFS4 operation, then opname ILLEGAL with opcode it used, like `ILLEGAL (4294967295)`. While this points to a bug in packet detection, such 'random' illegal opnames create multiple new operations that confuse kibana. Do not include opcode into opname ILLEGAL. Signed-off-by: Tigran Mkrtchyan <tigran.mkrtchyan@desy.de> (cherry picked from commit f457715)
andrewkroh
approved these changes
May 8, 2019
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.
Cherry-pick of PR #11503 to 7.x branch. Original message:
When we fail to map packet to a valid NFS4 operation, then opname
ILLEGAL with opcode it used, like
ILLEGAL (4294967295). Whilethis points to a bug in packet detection, such 'random' illegal
opnames create multiple new operations that confuse kibana.
Do not include opcode into opname ILLEGAL.
Signed-off-by: Tigran Mkrtchyan tigran.mkrtchyan@desy.de
(cherry picked from commit f457715)