Skip to content

access log: add response code details to the access log formatter#6626

Merged
lizan merged 4 commits intoenvoyproxy:masterfrom
eziskind:rcdetails
Apr 19, 2019
Merged

access log: add response code details to the access log formatter#6626
lizan merged 4 commits intoenvoyproxy:masterfrom
eziskind:rcdetails

Conversation

@eziskind
Copy link
Copy Markdown
Contributor

Description: add formatting for the "response code details" string recently added to the StreamInfo (#6530)
Risk Level: low
Testing: unit tests
Docs Changes: updated
Release Notes: updated

Signed-off-by: Elisha Ziskind eziskind@google.com

Signed-off-by: Elisha Ziskind <eziskind@google.com>
Signed-off-by: Elisha Ziskind <eziskind@google.com>
@htuch htuch requested a review from lizan April 17, 2019 18:45
@mattklein123
Copy link
Copy Markdown
Member

@eziskind drive by comment: would it be possible to also add this so the gRPC access log? In general we try to keep parity here. Thanks so much for adding this.

@lizan
Copy link
Copy Markdown
Member

lizan commented Apr 18, 2019

+1 on gRPC access logger parity

Signed-off-by: Elisha Ziskind <eziskind@google.com>
@eziskind
Copy link
Copy Markdown
Contributor Author

@eziskind drive by comment: would it be possible to also add this so the gRPC access log? In general we try to keep parity here. Thanks so much for adding this.

Done

@eziskind
Copy link
Copy Markdown
Contributor Author

/retest

@repokitteh-read-only
Copy link
Copy Markdown

🔨 rebuilding ci/circleci: release (failed build)

🐱

Caused by: a #6626 (comment) was created by @eziskind.

see: more, trace.

@eziskind
Copy link
Copy Markdown
Contributor Author

/retest

@repokitteh-read-only
Copy link
Copy Markdown

🔨 rebuilding ci/circleci: release (failed build)

🐱

Caused by: a #6626 (comment) was created by @eziskind.

see: more, trace.


1.11.0 (Pending)
================
* access log: added RESPONSE_CODE_DETAILS.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

nit: link to the doc (as well as gRPC field)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Done

@lizan lizan added the waiting label Apr 18, 2019
Signed-off-by: Elisha Ziskind <eziskind@google.com>
@lizan lizan merged commit 8789695 into envoyproxy:master Apr 19, 2019
@eziskind eziskind deleted the rcdetails branch April 19, 2019 13:38
mpuncel added a commit to mpuncel/envoy that referenced this pull request Apr 19, 2019
* master: (26 commits)
  docs: update docs to recommend /retest repokitteh command (envoyproxy#6655)
  http timeout integration test: wait for 15s for upstream reset (envoyproxy#6646)
  access log: add response code details to the access log formatter (envoyproxy#6626)
  build: add ppc build badge to README (envoyproxy#6629)
  Revert dispatcher stats (envoyproxy#6649)
  Batch implementation with timer (envoyproxy#6452)
  fault filter: reset token bucket on data start (envoyproxy#6627)
  event: update libevent dependency to fix race condition (envoyproxy#6637)
  examples: standardize docker-compose version and yaml extension (envoyproxy#6613)
  quiche: Implement SpdyUnsafeArena using SpdySimpleArena (envoyproxy#6612)
  router: support customizable retry back-off intervals (envoyproxy#6568)
  api: create OpenRCA service proto file (envoyproxy#6497)
  ext_authz: option for clearing route cache of authorized requests (envoyproxy#6503)
  build: update jinja to 2.10.1. (envoyproxy#6623)
  tools: check spelling in pre-push hook (envoyproxy#6631)
  security: blameless postmortem template. (envoyproxy#6553)
  Implementing Endpoint lease for ClusterLoadAssigment (envoyproxy#6477)
  add HTTP integration tests exercising timeouts (envoyproxy#6621)
  event: fix DispatcherImplTest::InitializeStats flake (envoyproxy#6619)
  Add tag extractor for RDS route config name (envoyproxy#6618)
  ...

Signed-off-by: Michael Puncel <mpuncel@squareup.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.

3 participants