-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Receiving bogus TLS handshakes when using K8s attributes processor on some namespaces #31370
Labels
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This was referenced Feb 27, 2024
This was referenced Mar 5, 2024
Hello @gebn, can you share the full configuration you're using? (Including the receiver and exporter configurations) |
Hi @crobert-1, will share as much as I'm able to, I'll get back to you towards the end of next week. |
TylerHelmuth
added
waiting for author
and removed
needs triage
New item requiring triage
labels
Mar 13, 2024
Frustratingly, I can no longer reproduce this. I will reopen if it happens again. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Component(s)
processor/k8sattributes
What happened?
Description
When monitoring a specific namespace with the k8sattributes processor, every 10s, two messages are printed at the same time from zapgrpc about "received bogus greeting from client". If I change the config to monitor another namespace instead, these messages are not printed. It reads as if something is trying to connect to the collector with TLS every 10s, and failing. There is no indication of source IP in the logs to verify what the client is. Changing the config alone would not trigger this, there must be something else going on.
Steps to Reproduce
Start the collector with
then change to
Expected Result
No "received bogus greeting from client" error messages, or at least the behaviour to be consistent when monitoring both namespaces.
Actual Result
"received bogus greeting from client" error messages when monitoring one namespace, and no such messages when monitoring the other.
Collector version
v0.94.0
Environment information
Official Docker image
OpenTelemetry Collector configuration
Log output
Additional context
No response
The text was updated successfully, but these errors were encountered: