You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
k8sattributes:
filter:
namespace: a
then change to
k8sattributes:
filter:
namespace: b
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.
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: