receivers' unknown type: "redfish" for id: "redfish"

[glimchb]

Component(s)

receiver/redfish

What happened?

Description

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

Steps to Reproduce

wget https://github.com/open-telemetry/opentelemetry-collector-releases/releases/download/v0.140.0/otelcol-contrib_0.140.0_linux_amd64.tar.gz

or

docker run --rm -it --privileged --network host -v $(pwd)/otel-collector-config.yaml:/etc/otelcol-contrib/config.yaml ghcr.io/open-telemetry/opentelemetry-collector-releases/opentelemetry-collector-contrib:0.140.1 

Expected Result

redfish receiver is included into contrib

Actual Result

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

Collector version

v0.140.1

Environment information

Environment

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

OpenTelemetry Collector configuration

receivers:
  redfish:
    collection_interval: 60s
    servers:
    - host: https://16.1.15.1
      username: "${BMC_USER}"
      password: "${BMC_PASSWORD}"
      insecure: true
      computer_system_id: "1"
      redfish:
        version: v1
      resources:
      - ComputerSystem
      - Fans

processors:
  batch: {}

exporters:
  debug:
     verbosity: detailed

extensions:
  health_check:

service:
  pipelines:
    metrics:
      receivers: [redfish]
      processors: [batch]
      exporters: [debug]

Log output

Additional context

No response

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}

[github-actions]

Pinging code owners:

• receiver/redfish: @steven-freed

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

[khushijain21]

I build the collector on main using make otelcontribcol and start the collector with above config - I don't see this error. What I see however is

'receivers' error reading configuration for "redfish": decoding failed due to the following error(s):

'servers[0]' has invalid keys: host
2025/11/20 12:35:43 collector server run finished with error: failed to get config: cannot unmarshal the configuration: decoding failed due to the following error(s):

'receivers' error reading configuration for "redfish": decoding failed due to the following error(s):

Looks like "host" was changed to "base_url" in this PR and the README.md was not updated. If you change it servers.[0].base_url the collector successfully starts

[glimchb]

@khushijain21 you are right when building from source. and thank you for the readme update 🥇

what needs to be done so it is included also in container images

ghcr.io/open-telemetry/opentelemetry-collector-releases/opentelemetry-collector-contrib:0.140.1

i also tried release binary - also missing : https://github.com/open-telemetry/opentelemetry-collector-releases/releases/download/v0.140.0/otelcol-contrib_0.140.0_linux_amd64.tar.gz

./otelcol-contrib -v
otelcol-contrib version 0.140.1

looks like #44425 is addressing similar issue with also recent new receiver ?

I also opened open-telemetry/opentelemetry-collector-releases#1271

[crobert-1]

The component is marked as development stability, which means it's likely not intended to be in the distribution yet. The usual process is to mark it as alpha and then include it in the contrib distribution. Please review the Adding New Components documentation for more information on new components being added to the disitribution.

@steven-freed Can you provide some more information on current status of this component, and do you have any thoughts as to when it would be available?

[steven-freed]

Hey that's correct this is still in development. I have been pulled into some other priorities at work but I do have JIRAs in my teams backlog to get an alpha release completed for monitoring our servers. The main logic is there but I need to transition the receiver to otel semantic hardware naming convention before releasing. I'd say maybe a couple months of time before an alpha release.