Add support for TLS in memcachedreceiver

[nitrotm]

Component(s)

receiver/memcached

Is your feature request related to a problem? Please describe.

When memcached is executed with --enable-ssl, the scraper must support TLS DialContext.

Describe the solution you'd like

Add the option to configure the TLS DialContext by adding new config settings. Probably the best is to embed the existing TLS config module

See here for a sample implementation when building a new memcache client (currently, the go dep is pointing to a fork of this project, but the fork lags behind in term of features).

Describe alternatives you've considered

No response

Additional context

No response

[github-actions]

Pinging code owners:

• receiver/memcached: @djaglowski

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• receiver/memcached: @djaglowski

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[djaglowski]

Makes sense to me. Will you make a PR @nitrotm?

[nitrotm]

do we know if that repo is still the best client implementation https://github.com/grobie/gomemcache?

sounds like the original author did some work since then (but still lacking the Stats command though):

This branch is 12 commits ahead of, 30 commits behind bradfitz/gomemcache:master.

[nitrotm]

that being said, grobie implementation has support for TLS, so maybe best to use that: grobie/gomemcache@331774f

[kernelpanic77]

@nitrotm I'd like contribute as well, let me know if there is anything I can do.