-
Notifications
You must be signed in to change notification settings - Fork 3k
Closed as not planned
Closed as not planned
Copy link
Labels
Description
Component(s)
exporter/loadbalancing
What happened?
Description
Using this exporter encounters a bug. I have tried dsn
and k8s
resolver; both cause bugs.
use dns resolver, config:
loadbalancing/jaeger:
routing_key: "traceID"
protocol:
otlp:
# all options from the OTLP exporter are supported, except the endpoint
timeout: 1s
tls:
insecure: true
sending_queue:
enabled: true
storage: file_storage/all_settings
retry_on_failure:
enabled: true
max_elapsed_time: 500s
resolver:
dns:
hostname: jaeger-collector-headless.insight-system.svc.cluster.local
port: "4317"
interval: 1s
timeout: 200ms
using k8s
resolver config:
loadbalancing/jaeger:
routing_key: "traceID"
protocol:
otlp:
# all options from the OTLP exporter are supported, except the endpoint
timeout: 1s
tls:
insecure: true
sending_queue:
enabled: true
storage: file_storage/all_settings
retry_on_failure:
enabled: true
max_elapsed_time: 500s
resolver:
k8s:
service: insight-jaeger-collector
ports:
- 4317
I have noticed this:
// something is really wrong... how come we couldn't find the exporter?? |
It also shows that something is wrong with the code.
Collector version
v0.109.0
Environment information
Environment
OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")
OpenTelemetry Collector configuration
No response
Log output
No response
Additional context
No response