-
Notifications
You must be signed in to change notification settings - Fork 5.5k
access log: add response flag filter #3536
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
Changes from 6 commits
1176b61
d379e04
05eb710
4cb95e0
0b4b631
d02b862
53697d5
e5ad2c8
4bb4afb
c421d95
aa5b20d
1c99b8a
bc18e7b
53662e8
3421855
64803c0
9ebe110
08bb66e
779af08
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -8,6 +8,8 @@ Version history | |
| * access log: added ability to format START_TIME. | ||
| * access log: added DYNAMIC_METADATA :ref:`access log formatter <config_access_log_format>`. | ||
| * access log: added :ref:`HeaderFilter <envoy_api_msg_config.filter.accesslog.v2.HeaderFilter>` | ||
| to filter logs based on request headers | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Move to 1.8.0 section. |
||
| * access log: added :ref:`response flag filter <envoy_api_msg_config.filter.accesslog.v2.ResponseFlagFilter>` to filter based on the presence of Envoy response flags. | ||
| to filter logs based on request headers. | ||
| * access log: gRPC Access Log Service (ALS) support added for :ref:`HTTP access logs | ||
| <envoy_api_msg_config.accesslog.v2.HttpGrpcAccessLogConfig>`. | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -208,6 +208,11 @@ class RequestInfo { | |
| */ | ||
| virtual bool getResponseFlag(ResponseFlag response_flag) const PURE; | ||
|
|
||
| /** | ||
| * @return whether any response flag is set or not. | ||
| */ | ||
| virtual bool getResponseFlag() const PURE; | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. nit: should this be
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. yeah I think that is a better name, and also a better name for the other function |
||
|
|
||
| /** | ||
| * @return upstream host description. | ||
| */ | ||
|
|
||
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.
alternatively I thought about adding an option to specify the flags you care about. But I think that response flags are important, and infrequent enough to have the filter filter on all of them. Thoughts?
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.
One way to achieve both settings is have an array field that will specify which response flags to log on and if that field is empty default to all response flags? (or have an enum that says all)
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.
Yeah +1 to what @ccaraman said. I would do that.
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.
Yep, that is what I thought, will add.