Skip to content

Extproc logging bits for Fail Open and Server Half Close#41691

Merged
adisuissa merged 48 commits intoenvoyproxy:mainfrom
melginaldi:extproc-logging-fail-open
Dec 23, 2025
Merged

Extproc logging bits for Fail Open and Server Half Close#41691
adisuissa merged 48 commits intoenvoyproxy:mainfrom
melginaldi:extproc-logging-fail-open

Conversation

@melginaldi
Copy link
Copy Markdown
Contributor

@melginaldi melginaldi commented Oct 24, 2025

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

…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>
@repokitteh-read-only
Copy link
Copy Markdown

As a reminder, PRs marked as draft will not be automatically assigned reviewers,
or be handled by maintainer-oncall triage.

Please mark your PR as ready when you want it to be reviewed!

🐱

Caused by: #41691 was opened by melginaldi.

see: more, trace.

@melginaldi melginaldi changed the title Extproc logging fail open Extproc logging bits for Fail Open and Server Half Close Oct 24, 2025
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>
@agrawroh
Copy link
Copy Markdown
Member

agrawroh commented Nov 3, 2025

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>
@melginaldi
Copy link
Copy Markdown
Contributor Author

@melginaldi this needs a main merge and conflict resolution

i think its also waiting on your feedback/iteration

/wait

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>
@yanjunxiang-google
Copy link
Copy Markdown
Contributor

LGTM

@adisuissa
Copy link
Copy Markdown
Contributor

hmmm... is this conflicting with #41602 ? Seems that the other PR is contained in this one.

@melginaldi
Copy link
Copy Markdown
Contributor Author

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?

@adisuissa
Copy link
Copy Markdown
Contributor

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>
@melginaldi
Copy link
Copy Markdown
Contributor Author

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.

Ack @adisuissa, done.

Copy link
Copy Markdown
Contributor

@adisuissa adisuissa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, one high-level question.

Comment thread source/extensions/filters/http/ext_proc/ext_proc.cc Outdated
Comment thread source/extensions/filters/http/ext_proc/ext_proc.cc Outdated
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>
@ravenblackx
Copy link
Copy Markdown
Contributor

Pinged @adisuissa but rapid response not expected because holiday time of year.

Copy link
Copy Markdown
Contributor

@adisuissa adisuissa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks!

@adisuissa adisuissa merged commit c7118f9 into envoyproxy:main Dec 23, 2025
25 checks passed
tyxia pushed a commit that referenced this pull request Feb 25, 2026
…#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>
bmjask pushed a commit to bmjask/envoy that referenced this pull request Mar 14, 2026
…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>
bvandewalle pushed a commit to bvandewalle/envoy that referenced this pull request Mar 17, 2026
…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>
grnmeira pushed a commit to grnmeira/envoy that referenced this pull request Mar 20, 2026
…y#41691)

Signed-off-by: Melissa Ginaldi <mginaldi@google.com>
Signed-off-by: Gustavo <grnmeira@gmail.com>
fishcakez pushed a commit to fishcakez/envoy that referenced this pull request Mar 25, 2026
…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>
krinkinmu pushed a commit to grnmeira/envoy that referenced this pull request Apr 20, 2026
…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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants