-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ext_proc: observability mode part 3: logging and billing support #34960
Merged
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
Signed-off-by: tyxia <tyxia@google.com>
Signed-off-by: tyxia <tyxia@google.com>
Signed-off-by: tyxia <tyxia@google.com>
/retest |
/assign @htuch @yanavlasov |
htuch
reviewed
Jul 3, 2024
htuch
reviewed
Jul 3, 2024
test/extensions/filters/http/ext_proc/ext_proc_integration_test.cc
Outdated
Show resolved
Hide resolved
htuch
reviewed
Jul 3, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM modulo nits.
Signed-off-by: tyxia <tyxia@google.com>
/retest |
htuch
approved these changes
Jul 3, 2024
cainelli
pushed a commit
to cainelli/envoy
that referenced
this pull request
Jul 5, 2024
…oyproxy#34960) There is no response in observability mode by design, so logging on onFinishProcessorCalls which is invoked on response won't work. Note, existing error/close case still work as normal Solution: Leverage the encodeComplete function to write the logging/billing info. This is also before the consumers (extensions/filters behind) reading it. Test: Existing Integration test frame with logging_test_filter as consumer Risk level: Low Signed-off-by: tyxia <tyxia@google.com> Signed-off-by: Fernando Cainelli <fernando.cainelli-external@getyourguide.com>
cainelli
pushed a commit
to cainelli/envoy
that referenced
this pull request
Jul 5, 2024
…oyproxy#34960) There is no response in observability mode by design, so logging on onFinishProcessorCalls which is invoked on response won't work. Note, existing error/close case still work as normal Solution: Leverage the encodeComplete function to write the logging/billing info. This is also before the consumers (extensions/filters behind) reading it. Test: Existing Integration test frame with logging_test_filter as consumer Risk level: Low Signed-off-by: tyxia <tyxia@google.com> Signed-off-by: Fernando Cainelli <fernando.cainelli-external@getyourguide.com>
cainelli
pushed a commit
to cainelli/envoy
that referenced
this pull request
Jul 5, 2024
…oyproxy#34960) There is no response in observability mode by design, so logging on onFinishProcessorCalls which is invoked on response won't work. Note, existing error/close case still work as normal Solution: Leverage the encodeComplete function to write the logging/billing info. This is also before the consumers (extensions/filters behind) reading it. Test: Existing Integration test frame with logging_test_filter as consumer Risk level: Low Signed-off-by: tyxia <tyxia@google.com> Signed-off-by: Fernando Cainelli <fernando.cainelli-external@getyourguide.com>
cainelli
pushed a commit
to cainelli/envoy
that referenced
this pull request
Jul 5, 2024
…oyproxy#34960) There is no response in observability mode by design, so logging on onFinishProcessorCalls which is invoked on response won't work. Note, existing error/close case still work as normal Solution: Leverage the encodeComplete function to write the logging/billing info. This is also before the consumers (extensions/filters behind) reading it. Test: Existing Integration test frame with logging_test_filter as consumer Risk level: Low Signed-off-by: tyxia <tyxia@google.com> Signed-off-by: Fernando Cainelli <fernando.cainelli-external@getyourguide.com>
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.
There is no response in observability mode by design, so logging on
onFinishProcessorCalls
which is invoked on response won't work. Note, existing error/close case still work as normalSolution: Leverage the
encodeComplete
function to write the logging/billing info. This is also before the consumers (extensions/filters behind) reading it.Test: Existing Integration test frame with
logging_test_filter
as consumer