Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Issue#18775

Answeredbyjtweaver
shivamsoni1 asked this question inGeneral
Issue#18775
Oct 5, 2023· 3 comments· 4 replies
Discussion options

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

You must be logged in to vote

Ah. It appears the source name should beotlp_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).

Replies: 3 comments 4 replies

Comment options

Hi@shivamsoni1 ,

It looks like you have a typo since the error message saysmy_sourc_id but the source id is actuallymy_source_id.

You must be logged in to vote
0 replies
Comment options

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:8686sources:  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: 300sinks:  console:    inputs:      - otlp_logs    target: stdout    type: console    encoding:      codec: json
You must be logged in to vote
4 replies
@jtweaver
Comment options

Here's the error:

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

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

@jtweaver
Comment options

Ah. It appears the source name should beotlp_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).

Answer selected bypront
@ToroNZ
Comment options

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

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" ]

Comment options

Yes - the need for a. in the input was not clear. But I too can confirm that i got same error message and then by adding.logs it went away.

## Before$ sudo vector validate /etc/vector/vector.yamlFailed to load ["/etc/vector/vector.yaml"]------------------------------------------x Input "otel_source" for sink "sink_otel" doesn't match any components.## After$ sudo vector validate /etc/vector/vector.yamlLoaded with warnings ["/etc/vector/vector.yaml"]------------------------------------------------~ Source "otel_source.metrics" has no consumers~ Source "otel_source.traces" has no consumers2025-11-21T14:42:53.772072Z  WARN sink{component_kind="sink" component_id=sink_otel component_type=opentelemetry}: vector::sinks::util::http: Option `headers` has been deprecated. Use `request.headers` instead.√ Component configuration√ Health check "sink_dynatrace_otel"√ Health check "console_out"------------------------------------------------                                       Validated
You must be logged in to vote
0 replies
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Category
General
Labels
source: opentelemetryAnything `opentelemetry` source related
5 participants
@shivamsoni1@jszwedko@ToroNZ@jtweaver@robertjahn
[8]ページ先頭
©2009-2025 Movatter.jp