Skip to content
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

Not able to get traces into kafka consumer from otel collector #34142

Open
edificeinsightworksapp opened this issue Jul 10, 2024 · 3 comments
Open
Labels
bug Something isn't working exporter/kafka question Further information is requested

Comments

@edificeinsightworksapp
Copy link

edificeinsightworksapp commented Jul 10, 2024

Hello,

Not able to get traces into Kafka consumer output from collector. please find the below otel-config file:
Our pipeline is from our app--otel-kafka, spans are getting generated and displayed in the otel output debug log. But not going to Kafka topic and no error msg either. If I post a msg directly to Kafka from any other producer, data is received to Kafka. Request to let me know what would be the issue or any way i can debug more?

Starting the collector with below command:

docker run -d \ -p 4317:4317 -v $(pwd)/otel-collector-config.yaml:/etc/otelcol/otel-collector-config.yaml \ otel/opentelemetry-collector:latest

otel-collector-config.yaml

receivers:
  otlp:
    protocols:
      grpc:

processors:
  batch:
  queued_retry:
 
exporters: 
  debug:
    verbosity: detailed
  kafka:
    brokers:
      - localhost:9092
    #topic: jaeger-spans
    protocol_version: 3.7.1
  logging:
    verbosity: detailed
    loglevel: debug
    
service:
  pipelines:
    traces:
      receivers: [otlp]
      processors: [batch]
      exporters: [debug,kafka,logging]
  telemetry:
    logs:
      level: "debug"
      encoding: "json"
      development: true

Thanks

@codeboten codeboten transferred this issue from open-telemetry/opentelemetry-collector Jul 17, 2024
@crobert-1 crobert-1 added exporter/kafka bug Something isn't working needs triage New item requiring triage labels Jul 17, 2024
Copy link
Contributor

Pinging code owners for exporter/kafka: @pavolloffay @MovieStoreGuy. See Adding Labels via Comments if you do not have permissions to add labels yourself.

@Frapschen
Copy link
Contributor

@edificeinsightworksapp Hi, please make sure your kafka brokers address work for your. Docker network is isolate, I don't think localhost:9092 is a right address to your kafak brokers

Copy link
Contributor

github-actions bot commented Oct 7, 2024

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Oct 7, 2024
@Frapschen Frapschen added question Further information is requested and removed needs triage New item requiring triage labels Oct 8, 2024
@github-actions github-actions bot removed the Stale label Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working exporter/kafka question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants