Issue

[shivamsoni1]

my vector.yaml file is -
sources:
my_source_id:
type: opentelemetry
grpc:
address: 0.0.0.0:4317
http:
address: 0.0.0.0:4318

sinks:
my_sink_id:
type: console
inputs:
- my_source_id
encoding:
codec: json

but getting this error Configuration error. error=Input "my_sourc_id" for sink "my_sink_id" doesn't match any components.

pls help

[jszwedko]

Hi @shivamsoni1 ,

It looks like you have a typo since the error message says my_sourc_id but the source id is actually my_source_id.

[jtweaver]

I'm also seeing this issue. It's not a typo. It appears to be a bug. Here's a simple full example:

api:
  enabled: true
  address: 0.0.0.0:8686
sources:
  otlp_logs:
    type: "opentelemetry"
    grpc:
      address: 0.0.0.0:4317
    http:
      address: 0.0.0.0:4318
      keepalive:
        max_connection_age_jitter_factor: 0.1
        max_connection_age_secs: 300
sinks:
  console:
    inputs:
      - otlp_logs
    target: stdout
    type: console
    encoding:
      codec: json

[jtweaver]

Here's the error:

ERROR vector::cli: Configuration error. error=Input "otlp_logs" for sink "console" doesn't match any components.

[jtweaver]

Also, my version: timberio/vector:0.36.0-debian

[jtweaver]

Ah. It appears the source name should be otlp_logs.logs. I didn't see this in the documentation of the source. Might be a common source of confusion. Especially since otlp metrics is not yet supported (per the docs).

[ToroNZ]

Good catch. There's also an example in the regression test cases:

vector/regression/cases/otlp_grpc_to_blackhole/vector/vector.yaml

Lines 11 to 30 in 9bd2593

	opentelemetry:
	type: "opentelemetry"
	http:
	address: "127.0.0.1:4318"
	grpc:
	address: "127.0.0.1:4317"
	##
	## Sinks
	##
	sinks:
	prometheus:
	type: "prometheus_exporter"
	inputs: [ "internal_metrics" ]
	address: "127.0.0.1:9090"
	socket_sink:
	type: "socket"
	inputs: [ "opentelemetry.logs" ]