Disables response logging as a default #42353
Merged
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.
Previously, if any of the following were true, we would log HTTP responses.
logging.json
was setlogging.dest
was setTTY
was detectedThe logging format should not dictate what is logged
Release Note: Responses are never logged by default. Previously, responses would be logged if either
logging.json
was true,logging.dest
was specified, or aTTY
was detected. To restore the previous behavior set logging.events.response=*` in kibana.yml.