Oliver Siegmar

Thanks for your contribution. The functionality will be part of the next non-patch release.

Those legacy MDC fields were removed in sleuth 3.0.0. See https://github.com/spring-cloud/spring-cloud-sleuth/issues/1221.

Version 4 introduced [MdcDataFieldMapper](https://github.com/osiegmar/logback-gelf/blob/master/src/main/java/de/siegmar/logbackgelf/mappers/MdcDataFieldMapper.java) that can be used to programmatically add any kind of filtering logic.

I don't exactly understand your use case. If you're using the API (not the XML configuration) you could easily use a custom field mapper for this. See https://github.com/osiegmar/logback-gelf/issues/78 for example....

Thanks for your request. An easy way how you could handle this right away: [de.siegmar.logbackgelf.GelfEncoder#addFieldMapper](https://github.com/osiegmar/logback-gelf/blob/v4.0.2/src/main/java/de/siegmar/logbackgelf/GelfEncoder.java#L271) ...just add a custom mapper in order to send the thread id as a separate...

Thanks for bringing this up! I doubt that configuring a trusted CA increases the security much as the domain name of the certificate (CN) is still not checked as defined...

Added certificate hostname verification (based on [RFC 6125](https://tools.ietf.org/html/rfc6125)) per 2960bc48396880183ac8a0e2ed60dbeafc40f4c5

@tparkercbn Not yet. As there was no feedback on the branch yet. It currently only contains server certificate whitelisting. I'm willing to invest more time on this if someone provides...

Related: https://github.com/Graylog2/graylog2-server/issues/5171

Which version of graylog-server do you use?