You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is actually possible. The logging.filter setting can be set to keys that should be removed from anything that gets logged. The filtering of the authorization header is accomplished by the default setting:
--logging.filter.authorization=remove
This causes the "authorization" key to be removed from any object logged by kibana. No matter where it appears, the logger will recurse through nested objects and remove any authorization key.
#5036 added the ability to filter auth headers from the logs, but I don't believe it allows the admin to customize what gets filtered.
This issue tracks allowing the admin to configure which headers are filtered out from the logs (e.g. as a setting in the kibana.yml).
If this is already possible, then :) and this issue can track adding the mechanism to the docs.
The text was updated successfully, but these errors were encountered: