-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[8.17] Kafka output panics unconditionally at startup #41823
Comments
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
The panic line is: beats/libbeat/outputs/kafka/client.go Line 167 in 367d94e
This must mean beats/libbeat/outputs/kafka/client.go Lines 116 to 129 in 367d94e
I also see Also it seems like the Kafka output isn't a NetworkClient output which means it doesn't use
It's not clear where the |
Reproduces shorlty after startup with the following minimal configuration: metricbeat.modules:
- module: system
metricsets:
- cpu
enabled: true
period: 1s
output.kafka:
hosts:
- localhost:9092
topic: test |
Reverting #40794 fixes it. |
beats/libbeat/outputs/outputs.go Lines 52 to 61 in 367d94e
The Connectable interface was changed to include a beats/libbeat/publisher/pipeline/client_worker.go Lines 64 to 70 in 367d94e
This bypasses the initial call to
|
Originally discovered in the diagnostics in elastic/elastic-agent#6049 (comment)
Detailed logs
The text was updated successfully, but these errors were encountered: