tlscheck receiver not working

[hlx-a1]

Component(s)

receiver/tlscheck

What happened?

Description

Trying to use the tlscheck receiver with container docker.io/otel/opentelemetry-collector-contrib:0.120.0-amd64@sha256:efc087bee79bd6f6f12842830186b31af8bea92f7935f4f6c136175a760d10cf results in the error attached to this issue.

Steps to Reproduce

1. Start otel collector with any valid config
2. Add a tlscheck receiver to the config like:

receivers:
  tlscheck:
    targets:
      - url: https://google.com

3. otel collector will no longer start

Expected Result

otel collector starts

Actual Result

otel collector fails to start

Collector version

v0.120.0

Environment information

Environment

OS: Rocky Linux

OpenTelemetry Collector configuration

Log output

error decoding 'receivers': unknown type: "tlscheck" for id: "tlscheck" (valid values: [hostmetrics expvar awscloudwatch bigip cloudfoundry otlpjsonfile rabbitmq skywalking haproxy httpcheck mongodbatlas nop apachespark collectd receiver_creator syslog jaeger k8s_cluster namedpipe nsxt postgresql windowseventlog chrony journald sqlquery wavefront active_directory_ds elasticsearch influxdb kubeletstats sapm tcplog awss3 jmx mysql opencensus otelarrow redis solace vcenter awsecscontainermetrics cloudflare googlecloudspanner podman_stats prometheus_simple splunk_hec k8sobjects libhoney mongodb prometheus statsd memcached apache azureblob docker_stats fluentforward googlecloudpubsub ntp oracledb kafka loki awscontainerinsightreceiver azureeventhub carbon github purefb riak awsxray filelog signalfx sshcheck zipkin zookeeper awsfirehose datadog splunkenterprise windowsperfcounters filestats udplog snmp aerospike flinkmetrics googlecloudmonitoring iis k8s_events webhookevent otlp nginx purefa snowflake sqlserver azuremonitor couchdb kafkametrics pulsar])

Additional context

No response

[github-actions]

Pinging code owners:

• receiver/tlscheck: @atoulme @michael-burt

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

[crobert-1]

Hello @hlx-a1, thanks for filing this issue! The tlscheck receiver is still considered to be development stability, which means it's not included in releases of the collector yet. Once it's marked as alpha it will be shipped with the released binary.

The code owners can provide more information regarding current state of development and a potential timeline for when the component will be alpha 👍

[hlx-a1]

Thanks, I guess this is working as intended so I will close the issue. Is there any kind of timeline for when I can expect this to get shipped in the releases? No worries if not.

[michael-burt]

Hi @hlx-a1 I am working on the PR to add this functionality, here is the link: #35823 (comment)

[hlx-a1]

I am getting almost exactly the same issue with docker.io/otel/opentelemetry-collector-contrib:0.122.0-amd64@sha256:a1836513d23899a33954c299d0ef38bb0b01c63160afbd888da513ee3d90e98c.
The release notes mention the that this component should be included now, so I'm not sure what's going wrong.

[michael-burt]

Yes, I have confirmed this behavior. I will follow up and see what went wrong.

[michael-burt]

I identified an issue which is likely the reason for this behavior: #38749

[atoulme]

Please see open-telemetry/opentelemetry-collector-releases#865 - contrib is built in opentelemetry-collector-releases.