-
Notifications
You must be signed in to change notification settings - Fork 108
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
beyla is overloading the external dns server with frequent ipv6 reverse lookups #895
Comments
We'll have a look on this, thank you for the report. In the meanwhile, you can disable the name resolver node with this line in your configuration file: name_resolver: null |
I managed to track this down a bit further in my local test environment - they all have to do with go_nethttp and go_grpc connection parsing - I see that this was recently changed with https://github.com/grafana/beyla/pull/725/files there are multiple possible problems b) even after this change, random strings are parsed as IPV6 addresses into the bpfConnectionInfoT struct
and grpc connections (this is in our own software)
ending up in the connection info (I am printing a string version of the connection struct - which should not make sense) |
Thanks for the input, @esara ! We will try to reproduce it locally and provide a fix. |
thanks for #1019 it helped to solve most of the problems, I still see bogus ipv6 addresses for go_grpc server spans
|
addressed by #1036 thanks! |
after upgrading from beyla v1.4 to beyla v1.5 or later, there is a significant dns lookups generated by beyla (instead of 100 dns lookup, it is generating 100k dns lookups) and most of them are for ipv6 reverse lookups
https://github.com/grafana/beyla/blob/main/pkg/transform/name_resolver.go#L149
added as part of
#745
The text was updated successfully, but these errors were encountered: