Getting error while running otelcol-contrib.exe from cmd #5760
Unanswered
saurabh-allocate
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
While running otelcol-contrib.exe from cmd I am getting below message:
2022/07/28 13:44:11 proto: duplicate proto type registered: jaeger.api_v2.PostSpansRequest
2022/07/28 13:44:11 proto: duplicate proto type registered: jaeger.api_v2.PostSpansResponse
Error: cannot create ConfigProvider: no Locations
2022/07/28 13:44:13 collector server run finished with error: cannot create ConfigProvider: no Locations
For backend I am using Jaeger for seeing traces and the application I am using is .NET application.
In Yaml file I have below content:
extensions:
memory_ballast:
size_mib: 512
zpages:
endpoint: 0.0.0.0:55679
health_check:
receivers:
hostmetrics:
collection_interval: 30s
scrapers:
cpu:
memory:
load:
otlp:
protocols:
grpc:
http:
processors:
batch/metrics:
timeout: 10s
send_batch_size: 1000
batch/logs:
send_batch_size: 100
batch:
timeout: 10s
memory_limiter:
# 75% of maximum memory up to 4G
limit_mib: 1536
# 25% of limit up to 2G
spike_limit_mib: 512
check_interval: 5s
exporters:
logging:
loglevel: debug
jaeger:
endpoint: "jaeger-all-in-one:14250"
traces:
span_name_as_resource_name: true
service:
pipelines:
traces:
receivers: [otlp]
processors: [memory_limiter, batch]
exporters: [logging, jaeger]
metrics:
receivers: [otlp]
processors: [memory_limiter, batch]
exporters: [logging, jaeger]
extensions: [memory_ballast, zpages, health_check]
telemetry:
logs:
level: "debug"
Beta Was this translation helpful? Give feedback.
All reactions