AIRSHIP-2978 Customisable Access Log formats #78
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
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.
Access Log format customisation
Make the default file access logger format configurable via the config file.
This will allow users to specify what they want to log in their access logs instead of just using the defaults we provide.
The default format remains unchanged though the fields were sorted in code to allow for easier grok'ing. It will be used if no format is provided in the config file.
Config Dump endpoint
Also added an optional
/configdumpendpoint to the health HTTP server enabled with--config-dump.This will dump the current Snapshot to JSON and can be useful to check what exactly Yggdrasil has going on without the constant
--debugoutput or running an entire Envoy instance.