-
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
my log files are flooded with a message regarding redis.go #35
Comments
It could be that that warning is indicating a real issue. What we mean by "transaction" is a request-reply pair not a transaction in the "sql sense". "Response from unknown transaction" could mean that we failed to parse the request or for some reason it wasn't sniffed. Would it be possible to send us a small tcpdump trace to [email protected]? We can then check what's going on exactly. |
It's normal because my redis don't transit any data Service is started but redis do nothing. |
Closing this one because in the meantime we've reduced the default logging verbosity. Many thanks for pointing out the issue. |
Same issue :( |
For reference. Follow up in #384 |
Update doc on how to configure dashboards in Kibana
Update Proc stats search in Kibana
…lastic#35) * Update vendored version of elastic/beats. * Update packer Makefile to not use xgo. * Move index template to root dir from etc * Remove -SNAPSHOT from version. It's added by packer.
* working integration v1(ILM issue exists in bit) * working v1 draft * Readme * expanded todos & remove datastream struct * Added csp k8s mounts to main agent manifests
* Port changes to kibana client from libbeat. elastic#31095 * Update to apmhttp/v2. Port changes from elastic#31072
I have this message in my log file:
usr/bin/packetbeat[26848]: redis.go:482: Response from unknown transaction. Ignoring.
It's just a warning, so I think more help is welcome for log configuration in packetbeat.conf.
For now I comment redis lines in protocols section because right know I don't have transaction.
The text was updated successfully, but these errors were encountered: