Collector fails to start with error in mongodb receiver invalid transport type ""

[ashish121092]

Using the following configuration for collector it fails to startup with error invalid configuration for mongodb receiver : invalid transport type "".

Collector image : otel/opentelemetry-collector-contrib:0.97.0

Collector configuration:

receivers:
  otlp:
    protocols:
      grpc:
      http:
  mongodb:
    hosts:
      - endpoint: 10.224.10.25:27017
      - endpoint: 10.224.10.28:27017
      - endpoint: 10.224.10.31:27017
    collection_interval: 60s
    initial_delay: 1s
    replica_set: rs0
    tls:
      insecure: true
      insecure_skip_verify: true

What is the expected behavior?

The mongodb receiver collects metrics from the hosts.

What is the actual behavior?

The collector fails to start with error invalid configuration for mongodb receiver. Invalid transport type "".

Error message : Error: invalid configuration: receivers::mongodb: invalid transport type ""; invalid transport type ""; invalid transport type ""
2024/04/05 17:05:32 collector server run finished with error: invalid configuration: receivers::mongodb: invalid transport type ""; invalid transport type ""; invalid transport type ""

[github-actions]

Pinging code owners for receiver/mongodb: @djaglowski @schmikei. See Adding Labels via Comments if you do not have permissions to add labels yourself.

[TylerHelmuth]

@ashish121092 please format your configuration and share the entire error message

[TylerHelmuth]

The issue is happening because you are specifying host configuration without specifying a transport protocol. If you do

mongodb:
  hosts:
    - endpoint: 10.224.10.25:27017
      transport: "tcp"
    - endpoint: 10.224.10.28:27017
      transport: "tcp"
    - endpoint: 10.224.10.31:27017
      transport: "tcp"

It should work.

[TylerHelmuth]

@djaglowski @schmikei this is happening because validation was added to confignet to ensure a transport type is set when using AddrConfig.

Reviewing the receiver, I don't see the component taking advantage of AddrConfig - it appears to be using it only to store an endpoint. Assuming that is true, I suggest you change the config struct to not depend on AddrConfig.

If you need to use AddrConfig I suggest documenting in the README that transport is required and possibly setting a default value if the user does not supply one. If only tcp should be supported you could use confignet.TCPAddrConfig.

[ashish121092]

@TylerHelmuth thanks it works after adding transport to the collector configuration.

[schmikei]

I think we should only be supporting TCP, if I have some extra time I can take a look at this

[sumoanema]

Have seen same issue in memcached receiver as well. Its not documented to use transport attribute in the config.

[TylerHelmuth]

@sumoanema please open a new issue, as this one was specifically for mongodb and was fixed