Currently Kibana is able to log requests, corresponding responses and various operations data (CPU, memory, disk, and other metrics). It's done with the help of even-better HapiJS plugin (fork of good plugin). As far as I can tell this information is only logged with logging.json: true.

Also there is additional logging.filter configuration value that allows Kibana to remove/censor some sensitive data from logs (e.g. authorization or cookie headers).

In the new-platform we're not going to use HapiJS so we'll have to handle this differently. So let's start from the following questions first:

• Are we still interested in all this data or is there anything we don't need anymore?
• What additional "service" data we'd like to log, but don't do right now? It's a good time for enhancement requests.
• Is "censoring" used primarily for authorization and cookie headers (i.e. only request/response use case)?

Any thoughts?

/cc @elastic/kibana-platform @elastic/kibana-operations

Tasks:

• Add a logging.filter config Implement filtering mechanism in the Logging service #57547
• Log ops metrics [logging/metrics] Provide ability to log ops data from core metrics service #86162
• Add request/response data