Extproc logging bits for Fail Open and Server Half Close#41691
Extproc logging bits for Fail Open and Server Half Close#41691adisuissa merged 48 commits intoenvoyproxy:mainfrom
Conversation
…in FilterState Signed-off-by: Melissa Ginaldi <mginaldi@google.com>
Signed-off-by: Melissa Ginaldi <mginaldi@google.com>
…resp-contreplace Signed-off-by: Melissa Ginaldi <mginaldi@google.com>
Signed-off-by: Melissa Ginaldi <mginaldi@google.com>
Signed-off-by: Melissa Ginaldi <mginaldi@google.com>
…resp-contreplace Signed-off-by: Melissa Ginaldi <mginaldi@google.com>
…resp-contreplace Signed-off-by: Melissa Ginaldi <mginaldi@google.com>
Signed-off-by: Melissa Ginaldi <mginaldi@google.com>
…resp-contreplace Signed-off-by: Melissa Ginaldi <mginaldi@google.com>
Signed-off-by: Melissa Ginaldi <mginaldi@google.com>
Signed-off-by: Melissa Ginaldi <mginaldi@google.com>
Signed-off-by: Melissa Ginaldi <mginaldi@google.com>
Signed-off-by: Melissa Ginaldi <mginaldi@google.com>
…resp-contreplace Signed-off-by: Melissa Ginaldi <mginaldi@google.com>
Signed-off-by: Melissa Ginaldi <mginaldi@google.com>
…resp-contreplace Signed-off-by: Melissa Ginaldi <mginaldi@google.com>
Signed-off-by: Melissa Ginaldi <mginaldi@google.com>
…l-open Signed-off-by: Melissa Ginaldi <mginaldi@google.com>
Signed-off-by: Melissa Ginaldi <mginaldi@google.com>
Signed-off-by: Melissa Ginaldi <mginaldi@google.com>
…resp-contreplace Signed-off-by: Melissa Ginaldi <mginaldi@google.com>
|
cc @yanjunxiang-google Could you please do a first pass? /wait-any |
Signed-off-by: Melissa Ginaldi <mginaldi@google.com>
Signed-off-by: Melissa Ginaldi <mginaldi@google.com>
Signed-off-by: Melissa Ginaldi <mginaldi@google.com>
Done - I have merged and resolved open comments |
Signed-off-by: Melissa Ginaldi <mginaldi@google.com>
…resp-contreplace Signed-off-by: Melissa Ginaldi <mginaldi@google.com>
…l-open Signed-off-by: Melissa Ginaldi <mginaldi@google.com>
…ng-fail-open Signed-off-by: Melissa Ginaldi <mginaldi@google.com>
Signed-off-by: Melissa Ginaldi <mginaldi@google.com>
|
LGTM |
|
hmmm... is this conflicting with #41602 ? Seems that the other PR is contained in this one. |
Yeah, this branch (extproc_logging_fail_open) is branched off of extproc_logging_immresp_contrep. It's a sub branch of the other so I assume I need to submit the other one first? |
After the other PR was merged, the current files currently have conflicts. Once it's cleaned up and pushed, we can approve it. |
Signed-off-by: Melissa Ginaldi <mginaldi@google.com>
Ack @adisuissa, done. |
adisuissa
left a comment
There was a problem hiding this comment.
Thanks, one high-level question.
Signed-off-by: Melissa Ginaldi <mginaldi@google.com>
Signed-off-by: Melissa Ginaldi <mginaldi@google.com>
…l-open Signed-off-by: Melissa Ginaldi <mginaldi@google.com>
|
Pinged @adisuissa but rapid response not expected because holiday time of year. |
…#43558) Commit Message: Track fail open behavior and processing effects to request headers as part of ExtAuthzLoggingInfo to match parity with ext_proc filter. Additional Description: This information will be used by ServiceExtensions for debugging/enhanced monitoring. This functionality was added to the ext_proc filter in #41295 and #41691, these bits are to keep parity with the ext_proc filter. last_req_processing_effect will hold the value of the last mutation event the filter completed on the request headers, whether successful or not. Therefore if 5 headers were successfully added but the 6 was invalid and the filter stopped processing any further mutations, the value of last_processing_effect will be InvalidMutationRejected. Risk Level:Low Testing:Tested in unit/integration tests Release Notes: Added new tracking bit last_req_processing_effect and failed_open to ExtAuthzLoggingInfo Filter State to track mutation events and failed_open occurrences. Docs Changes: N/A Platform Specific Features: N/A /assign @tyxia --------- Signed-off-by: Melissa Ginaldi <mginaldi@google.com>
…envoyproxy#43558) Commit Message: Track fail open behavior and processing effects to request headers as part of ExtAuthzLoggingInfo to match parity with ext_proc filter. Additional Description: This information will be used by ServiceExtensions for debugging/enhanced monitoring. This functionality was added to the ext_proc filter in envoyproxy#41295 and envoyproxy#41691, these bits are to keep parity with the ext_proc filter. last_req_processing_effect will hold the value of the last mutation event the filter completed on the request headers, whether successful or not. Therefore if 5 headers were successfully added but the 6 was invalid and the filter stopped processing any further mutations, the value of last_processing_effect will be InvalidMutationRejected. Risk Level:Low Testing:Tested in unit/integration tests Release Notes: Added new tracking bit last_req_processing_effect and failed_open to ExtAuthzLoggingInfo Filter State to track mutation events and failed_open occurrences. Docs Changes: N/A Platform Specific Features: N/A /assign @tyxia --------- Signed-off-by: Melissa Ginaldi <mginaldi@google.com> Signed-off-by: bjmask <11672696+bjmask@users.noreply.github.com>
…envoyproxy#43558) Commit Message: Track fail open behavior and processing effects to request headers as part of ExtAuthzLoggingInfo to match parity with ext_proc filter. Additional Description: This information will be used by ServiceExtensions for debugging/enhanced monitoring. This functionality was added to the ext_proc filter in envoyproxy#41295 and envoyproxy#41691, these bits are to keep parity with the ext_proc filter. last_req_processing_effect will hold the value of the last mutation event the filter completed on the request headers, whether successful or not. Therefore if 5 headers were successfully added but the 6 was invalid and the filter stopped processing any further mutations, the value of last_processing_effect will be InvalidMutationRejected. Risk Level:Low Testing:Tested in unit/integration tests Release Notes: Added new tracking bit last_req_processing_effect and failed_open to ExtAuthzLoggingInfo Filter State to track mutation events and failed_open occurrences. Docs Changes: N/A Platform Specific Features: N/A /assign @tyxia --------- Signed-off-by: Melissa Ginaldi <mginaldi@google.com>
…y#41691) Signed-off-by: Melissa Ginaldi <mginaldi@google.com> Signed-off-by: Gustavo <grnmeira@gmail.com>
…envoyproxy#43558) Commit Message: Track fail open behavior and processing effects to request headers as part of ExtAuthzLoggingInfo to match parity with ext_proc filter. Additional Description: This information will be used by ServiceExtensions for debugging/enhanced monitoring. This functionality was added to the ext_proc filter in envoyproxy#41295 and envoyproxy#41691, these bits are to keep parity with the ext_proc filter. last_req_processing_effect will hold the value of the last mutation event the filter completed on the request headers, whether successful or not. Therefore if 5 headers were successfully added but the 6 was invalid and the filter stopped processing any further mutations, the value of last_processing_effect will be InvalidMutationRejected. Risk Level:Low Testing:Tested in unit/integration tests Release Notes: Added new tracking bit last_req_processing_effect and failed_open to ExtAuthzLoggingInfo Filter State to track mutation events and failed_open occurrences. Docs Changes: N/A Platform Specific Features: N/A /assign @tyxia --------- Signed-off-by: Melissa Ginaldi <mginaldi@google.com>
…envoyproxy#43558) Commit Message: Track fail open behavior and processing effects to request headers as part of ExtAuthzLoggingInfo to match parity with ext_proc filter. Additional Description: This information will be used by ServiceExtensions for debugging/enhanced monitoring. This functionality was added to the ext_proc filter in envoyproxy#41295 and envoyproxy#41691, these bits are to keep parity with the ext_proc filter. last_req_processing_effect will hold the value of the last mutation event the filter completed on the request headers, whether successful or not. Therefore if 5 headers were successfully added but the 6 was invalid and the filter stopped processing any further mutations, the value of last_processing_effect will be InvalidMutationRejected. Risk Level:Low Testing:Tested in unit/integration tests Release Notes: Added new tracking bit last_req_processing_effect and failed_open to ExtAuthzLoggingInfo Filter State to track mutation events and failed_open occurrences. Docs Changes: N/A Platform Specific Features: N/A /assign @tyxia --------- Signed-off-by: Melissa Ginaldi <mginaldi@google.com>
Commit Message: Add bits to the FilterState in ExtProcLoggingInfo for when a stream fails-open or a server half close happens. Fail open we want to know which specific streams failed open, this is a highly requested visibility stat by service extension customers. Server Half close is a counter.
Additional Description: These bits will be useful for internal debugging and filtering metrics. This is build off of #41602
Risk Level: Low
Testing: Unit Integration tests
Docs Changes: N/A
Release Notes: Add new bits into ExtProcLoggingInfo for tracking fail-open occurrences.
Platform Specific Features: N/A
/assign @yanjunxiang-google