Muting an extremely chatty log line. #33
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
ctiller
added a commit
that referenced
this pull request
Jan 15, 2015
Muting an extremely chatty log line.
jtattermusch
pushed a commit
that referenced
this pull request
Jun 18, 2016
Fixed endpoint tests. Also more boolification.
apolcyn
referenced
this pull request
in apolcyn/grpc
Jul 25, 2016
Changed teeny weeny font for protobuf landing page snippet
lidizheng
referenced
this pull request
in lidizheng/grpc
Feb 12, 2021
There are multiple uses for opaque metadata that is associated with the specific listener/filter chain/route that a request matches on: 1. Logging. Similar to header values, we can log the metadata values. A listener might belong to a higher level concept in the configuration language that generated LDS protos, e.g. there might be a rule identifier expressed. This metadata allows logs to reflect the rule identifier. 2. Future custom stats backends might use metadata to guide where and how stats are emitted. E.g. the metadata might include information about which stats collector to emit to. 3. Proprietary filters can receive additional inputs via the metadata. The per-filter metadata generalizes and replaces the opaque_config in RDS ForwardAction. The metadata is structured such that each filter's metadata is under the reverse DNS namespace defined by the filter. Shared metadata may be arranged by coordinating on the reverse DNS namespace. As an example, the "envoy.http_connection_manager.access_log" filter namespace is suggested to be used for HTTP access logging. Fixes #33.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
No description provided.