search

SeldonIO / seldon-core

An MLOps framework to package, deploy, monitor and manage thousands of production machine learning models
https://www.seldon.io/tech/products/core/
Other
4.38k stars 831 forks source link

otel-collector-1 container not starting: error decoding 'exporters': unknown type: "jaeger" for id: "jaeger" #5189

Closed avolts closed 9 months ago

avolts commented 9 months ago

Describe the bug

After following the installation guide for Docker Compose for SeldenCoreV2, the otel-collector-1 container cannot start due to the following error: error decoding 'exporters': unknown type: "jaeger" for id: "jaeger" (valid values: [opensearch prometheus awsxray azuredataexplorer azuremonitor carbon cassandra mezmo sentry file honeycombmarker opencensus sumologic sapm skywalking alertmanager alibabacloud_logservice awscloudwatchlogs dataset googlecloud pulsar datadog f5cloud loadbalancing logicmonitor logzio logging clickhouse loki debug otlp awsemf coralogix instana tencentcloud_logservice dynatrace elasticsearch googlecloudpubsub prometheusremotewrite signalfx otlphttp awskinesis awss3 googlemanagedprometheus influxdb kafka splunk_hec syslog zipkin])

To reproduce

  1. Follow the installation instructions for Docker Compose https://docs.seldon.io/projects/seldon-core/en/v2/contents/getting-started/docker-installation/index.html and set CUSTOM_IMAGE_TAG=2.6.0
  2. Check running containers in Docker Desktop
  3. See that otel-collector-1 cannot start

Expected behaviour

I expect that the otel-collector-1 container is starting without issues after local deployment. Replacing jaeger with otlp at the marked places in the otel-collector-config.yaml solves the issue. "jaeger" is no longer in the exporters values. image

Environment

sakoush commented 9 months ago

A potential fix is described here

a workaround for now is to use an older version of otel/jeager via setting JAEGER_IMG=jaegertracing/all-in-one:1.49

lc525 commented 9 months ago

This is believed to be fixed via #5291