v0.122.0 Does Not Include New Components

[michael-burt]

Component(s)

cmd/otelcontribcol

What happened?

Description

New release (0.122.0) does not include new components

Steps to Reproduce

cat <<EOF > conf.yaml
receivers:
  tlscheck:
    targets:
      - endpoint: "google.com:443"
    interval: 30s

processors:
  batch:

exporters:
  logging:
    loglevel: debug

service:
  pipelines:
    metrics:
      receivers: [tlscheck]
      processors: [batch]
      exporters: [logging]
EOF

docker run -it --name otel-collector -v ./conf.yaml:/etc/otelcol/config.yaml --network host otel/opentelemetry-collector-contrib:0.122.0 --config /etc/otelcol/config.yaml

Expected Result

I expect the tlscheckreceiver to be installed in v0.122.0

I believe the problem is that this line was not updated during prep for 0.122.0

Collector version

0.122.0

Environment information

Environment

OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")

OpenTelemetry Collector configuration

receivers:
  tlscheck:
    targets:
      - endpoint: "google.com:443"
    interval: 30s

processors:
  batch:

exporters:
  logging:
    loglevel: debug

service:
  pipelines:
    metrics:
      receivers: [tlscheck]
      processors: [batch]
      exporters: [logging]

Log output

Error: failed to get config: cannot unmarshal the configuration: decoding failed due to the following error(s):

error decoding 'receivers': unknown type: "tlscheck" for id: "tlscheck" (valid values: [cloudflare cloudfoundry docker_stats github kubeletstats k8s_events postgresql pulsar rabbitmq signalfx syslog windowsperfcounters active_directory_ds namedpipe skywalking zookeeper expvar awsfirehose kafkametrics receiver_creator solace flinkmetrics kafka memcached nsxt sapm prometheus_simple zipkin otlp couchdb datadog googlecloudpubsub jmx mongodb otlpjsonfile otelarrow influxdb mongodbatlas mysql sshcheck wavefront snmp journald k8s_cluster awscontainerinsightreceiver azuremonitor bigip haproxy opencensus oracledb loki netflow purefb redis udplog vcenter windowseventlog awsecscontainermetrics azureeventhub googlecloudmonitoring ntp splunk_hec sqlserver tcplog nop aerospike apache collectd filelog filestats fluentforward iis carbon jaeger riak snowflake awsxray hostmetrics libhoney prometheus webhookevent awss3 googlecloudspanner nginx splunkenterprise sqlquery statsd k8sobjects chrony elasticsearch envoyals httpcheck podman_stats purefa apachespark awscloudwatch azureblob])
error decoding 'exporters': the logging exporter has been deprecated, use the debug exporter instead
2025/03/18 16:03:27 collector server run finished with error: failed to get config: cannot unmarshal the configuration: decoding failed due to the following error(s):

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

Additional context

No response

[crobert-1]

The tlscheck receiver isn't included in the contrib release because it's not in the release manifest. If this component is meant to be included in releases, please follow the steps for releasing new components. 👍

I'm not very familiar with the builder, but I do think there's a valid issue here that the version update was missed in the builder. This was updated for v0.121.1-dev before v0.121.0 was released, but it wasn't updated in any of the update PRs for v0.122.0.

[github-actions]

Pinging code owners for receiver/tlscheck: @atoulme @michael-burt. See Adding Labels via Comments if you do not have permissions to add labels yourself. For example, comment '/label priority:p2 -needs-triaged' to set the priority and remove the needs-triaged label.

[ocraviotto]

I was coming to ask about why if both the tcpcheckreceiver and the tlscheckreceiver were promoted to alpha stability, they still weren't included in the contrib manifest.

Following the Adding New Components section, in particular

Once your component has reached Alpha stability, you may also submit a PR to the OpenTelemetry Collector Releases repository to include your component in future releases of the OpenTelemetry Collector contrib distribution.

I noticed that there is a PR opened for the tcpcheckreceiver: open-telemetry/opentelemetry-collector-releases#865

However there is nothing yet for the tlscheckreceiver.