Align correlationID filter with LogContext::getCorrelationId()
This PR is a bit tricky about correctness. From a CorrelationIdFilter, the FieldName can be defined and it behaves locally correct. However, LogContext::getCorrelationId() mandates the field Fields.CORRELATION_ID for the correlationId.
It can be seen differently - I prepared a PR instead of an Issue since I personally tend to change it.
I classify the change as a low risk that only applies in case a custom correlation id header field is used.
As I have learned in a call: There are use-cases that set own LogContext fields and therfor, the behavior is as expected and a change would break existing consumers.
Align correlationID filter with LogContext::getCorrelationId()
This PR is a bit tricky about correctness. From a CorrelationIdFilter, the FieldName can be defined and it behaves locally correct. However, LogContext::getCorrelationId() mandates the field Fields.CORRELATION_ID for the correlationId.
It can be seen differently - I prepared a PR instead of an Issue since I personally tend to change it. I classify the change as a low risk that only applies in case a custom correlation id header field is used.