deepflowio
[BUG] mysql 协议的请求状态为 unknown
Search before asking
- [X] I had searched in the issues and found no similar feature requirement.
DeepFlow Component
Agent
What you expected to happen
How to reproduce
No response
DeepFlow version
Agent:Name: deepflow-agent community edition Branch: v6.6.4 CommitId: 958a449602f6892b494ad32be3867ff1f3b77823 RevCount: 11092 Compiler: rustc 1.77.1 (7cf61ebde 2024-03-27) CompileTime: 2024-08-30 02:48:44
Server:Name: deepflow-server community edition Branch: v6.6.4 CommitID: 6d70ea94436eb89fb3f0f1d3b45fbca15375f45c RevCount: 11095 Compiler: go version go1.21.13 linux/amd64 CompileTime: 2024-09-12 06:53:08
DeepFlow agent list
No response
Kubernetes CNI
No response
Operation-System/Kernel version
5.4.119-19-0009.11
Anything else
No response
Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
Code of Conduct
- [X] I agree to follow this project's Code of Conduct
我的环境使用了最新的deepflow v6.6.6版本，也存在类似的情况，存在unknown的协议不仅仅有mysql，还有redis、kafka、http等
- 目前已经在deepflow-agent-group-config.yaml中，调大到l7_log_packet_size=4096 ，问题依然存在；
- 应研发老师要求，在涉及kafka协议的容器里进行抓包，这两个文件 是在容器里抓到kafka端口9092的包 ，抓包命令（ tcpdump -i eth0 -vnn dst port 9092 -w /tmp/kafka_
hostname.cap）
@yujianweilai pcap中的流量仅有kafka的请求，所有日志中响应状态为未知。日志会反应流量的实际情况，从pcap看这个结果是预期的
