TCP version of HTTP Check Receiver

[Breee]

Component(s)

No response

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

I'd like to migrate from elastic heartbeats to otel collector, https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/httpcheckreceiver is perfect for that i think, it is however missing the possibility to check TCP endpoints

Describe the solution you'd like

Someone already proposed it, however it just got closed down sadly #20738

It would be great to have something along the lines of:

receivers:
  tcpcheck:
    endpoint: notdefault:1313
    transport: tcp
    collection_interval: 15s

Describe alternatives you've considered

No response

Additional context

No response

[github-actions]

Pinging code owners for receiver/httpcheck: @codeboten. 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/httpcheck: @codeboten

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

[StephanSalas]

This should be a different receiver right @Breee? TCP is not the same as HTTP from my perspective.. There is a TCP Receiver here: #34458

[atoulme]

Closing, let's reopen #20738