Improve logging for circuit breakers

[lanerjo]

Logs should be more detailed about the circuit breaker when tripped.

Existing log example:

"Caused by: org.elasticsearch.common.breaker.CircuitBreakingException: [parent] Data too large, data for [cluster:monitor/nodes/info[n]] would be [33958682092/31.6gb], which is larger than the limit of [32386737766/30.1gb], real usage: [33958603128/31.6gb], new bytes reserved: [78964/77.1kb], usages [request=0/0b, fielddata=0/0b, in_flight_requests=78964/77.1kb, accounting=0/0b]",

Log should include name of circuit breaker that was broken, [parent] is not descriptive enough.
Should include information about the request that tripped the circuit breaker. When you have hundreds of requests per second, it is nearly impossible to tell which request or request type tripped the breaker.

[elasticmachine]

Pinging @elastic/es-core-infra (:Core/Infra/Circuit Breakers)

[elasticmachine]

Pinging @elastic/es-core-infra (:Core/Infra/Logging)

[soarescaique]

Can I have this issue?

[pgomulka]

@soarescaique sure, feel free to submit PRs. Or if you prefer you can start with discussing the approach you want to take here.

[Kiriakos1998]

Hello @pgomulka, is this issue still open? If yes, I would like trying solving it.