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

exporter kafka cause otel-collector start fail #31677

Closed
zhboseu opened this issue Mar 11, 2024 · 4 comments
Closed

exporter kafka cause otel-collector start fail #31677

zhboseu opened this issue Mar 11, 2024 · 4 comments
Labels

Comments

@zhboseu
Copy link

zhboseu commented Mar 11, 2024

Component(s)

exporter/kafka

What happened?

Description

exporter kafka cause otel-collector start fail, both rpc port and http port start fail, report Connection closed

Steps to Reproduce

Expected Result

Actual Result

telnet 127.0.0.1 4317

Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Connection closed by foreign host

Collector version

0.96.0

Environment information

Environment

OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")

OpenTelemetry Collector configuration

receivers:
  otlp:
    protocols:
      # 4317
      grpc:
      # 4318
      http:

processors:
  memory_limiter:
    check_interval: 1s
    limit_mib: 5000
    spike_limit_mib: 1000

  batch:
    send_batch_max_size: 0
    send_batch_size: 8192
    timeout: 200ms

exporters:
  kafka:
    protocol_version: 2.0.0
    brokers:
      - "kafka:9092"
    auth:
      tls:
        insecure: true
        insecure_skip_verify: true
    encoding: otlp_proto
    retry_on_failure:
      enabled: true
      initial_interval: 5s
      max_interval: 30s
      max_elapsed_time: 120s
    sending_queue:
      enabled: true
      num_consumers: 10
      queue_size: 100

extensions:
  health_check:
    path: "/health/status"
    check_collector_pipeline:
      enabled: true
      interval: "1m"
      exporter_failure_threshold: 5

service:
  extensions: [health_check]
  telemetry:
    logs:
      level: "debug"
      development: true
    metrics:
      address: 0.0.0.0:8888
  pipelines:
    traces:
      receivers: [otlp]
      processors: [memory_limiter,batch]
      exporters: [kafka]

Log output

2024-03-11T14:13:04.309+0800	info	service@v0.96.0/telemetry.go:55	Setting up own telemetry...
2024-03-11T14:13:04.309+0800	info	service@v0.96.0/telemetry.go:97	Serving metrics	{"address": "0.0.0.0:8888", "level": "Basic"}
2024-03-11T14:13:04.309+0800	debug	extension@v0.96.0/extension.go:165	Beta component. May change in the future.	{"kind": "extension", "name": "health_check"}
2024-03-11T14:13:04.309+0800	debug	exporter@v0.96.0/exporter.go:273	Beta component. May change in the future.	{"kind": "exporter", "data_type": "traces", "name": "kafka"}

Additional context

No response

@zhboseu zhboseu added bug Something isn't working needs triage New item requiring triage labels Mar 11, 2024
Copy link
Contributor

Pinging code owners:

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

@crobert-1
Copy link
Member

It looks like this is a kafka error, not the collector.

https://stackoverflow.com/questions/45943571/diagnosing-kafka-connection-problems

@crobert-1 crobert-1 added question Further information is requested and removed bug Something isn't working needs triage New item requiring triage labels Mar 12, 2024
Copy link
Contributor

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 May 13, 2024
Copy link
Contributor

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants