-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
opentelementry的示例问题 #115
Labels
good first issue
Good for newcomers
Comments
@rogerogers @CoderPoet Please take a look. |
是的,新版本 jaeger 原生支持 OTLP 协议投递,jaeger exporter已经被移除了。 |
exporters:
otlp:
endpoint: jaeger-all-in-one:4317
tls:
insecure: true 改成 otlp 应该ok的。 |
十分感谢!问题解决!!! |
重新打开,原因是使用 otel 的地方需要修改此配置 |
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
用wsl2建立了docker-compose.yml和otel-collector-config.yaml运行之后,有一个容器:opentelemetry-collector一直运行不起来
示例:
本地建立yaml文件:
docker运行:
报错日志:
看日志的意思好像是opentelemetry-collector 支持的export中不含有jaeger,有效的是这些:(valid values: [skywalking sumologic dynatrace prometheusremotewrite sapm tanzuobservability prometheus awscloudwatchlogs carbon f5cloud googlemanagedprometheus influxdb otlp otlphttp clickhouse datadog instana loadbalancing loki opencensus logging splunk_hec tencentcloud_logservice parquet awsxray azuremonitor cassandra googlecloudpubsub zipkin awss3 file logicmonitor signalfx coralogix azuredataexplorer elasticsearch googlecloud pulsar sentry alibabacloud_logservice awskinesis dataset kafka logzio mezmo awsemf])
定位到otel-collector-config.yaml中的配置:
里面指定的exporters确实指定了jaeger
问题猜测:
是不是版本问题,otel-collector的最新版本中exporters不支持jaeger了?
The text was updated successfully, but these errors were encountered: