Adding support for SNI to filebeat

We would like to have filebeat use SNI when connecting to our server. We reach our server via the aaa.com domain, but it only has a TLS cert for bbb.com. We would like to tell filebeat to connect to the server using aaa.com, but to expect a cert for bbb.com when performing a TLS handshake.

I was thinking this might look something like:

output:
    elasticsearch:
        tls:
            server_name: "bbb.com"

and then the parameter would get slotted into https://github.com/elastic/beats/blob/master/libbeat/common/transport/tlscommon/config.go#L87 somehow.

I am happy to write the patch - would it be likely to be accepted? Thanks!

Hi Elastic team - what do I need to do to move this along? The CONTRIBUTING guide for Beats told me to ask here before starting work on my feature. Thanks.

Hi! Sorry for the late response. Please feel free to push the PR! The team will review it for sure!