Allow configuration of different (i.e. json) escaping for access log #192
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.
Thanks for contributing to the
capi_release
. To speed up the process of reviewing your pull request please provide us with:A short explanation of the proposed change:
With this PR the characters escaping used for logging variables to the nginx access log can be set to
json
. This allows changing the log format to a JSON string (e.g.{"key":"$variable"}
) and getting properly escaped JSON logs.An explanation of the use cases your change solves
With Logstash the parsing of JSON-formatted logs becomes easier and is more flexible (i.e. adding a new field does not require the parser to be changed).
Links to any other associated PRs
I have viewed signed and have submitted the Contributor License Agreement
I have made this pull request to the
develop
branchI have run CF Acceptance Tests on bosh lite