Kmeshctl v1.1.0-alpha long connection

[hzxuzhonghu]

What happened:

Deployed application here and enabled monitoring by kmeshctl monitoring --all enable

#1350 (comment)

I could not see access logs printed periodically. Only see

accesslog: 2025-05-08 03:10:31.010141453 +0000 UTC src.addr=10.244.0.12:38880, src.workload=ws-client, src.namespace=default, dst.addr=10.244.0.11:8080, dst.service=ws-server-service.default.svc.cluster.local, dst.workload=ws-server, dst.namespace=default, start_time=2025-05-08 03:10:31.010065899 +0000 UTC, direction=OUTBOUND, state=BPF_TCP_ESTABLISHED, sent_bytes=1, received_bytes=0, packet_loss=0, retransmissions=0, srtt=344us, min_rtt=43us, duration=0.075554ms
accesslog: 2025-05-08 03:10:31.010168719 +0000 UTC src.addr=10.244.0.12:38880, src.workload=ws-client, src.namespace=default, dst.addr=10.244.0.11:8080, dst.service=ws-server-service.default.svc.cluster.local, dst.workload=ws-server, dst.namespace=default, start_time=2025-05-08 03:10:31.010168405 +0000 UTC, direction=INBOUND, state=BPF_TCP_ESTABLISHED, sent_bytes=1, received_bytes=0, packet_loss=0, retransmissions=0, srtt=288us, min_rtt=36us, duration=0.000314ms

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• Kmesh version:
• Kmesh mode(kmesh has Kernel-Native Mode and Duel-Engine Mode):
• Istio version:
• Kernel version:
• Others:

[hzxuzhonghu]

cc @yp969803

[hzxuzhonghu]

Oh， i found that kmeshctl monitoring --connectionMetrics enable need to be explicitly run. connectionMetrics is not enabled by kmeshctl monitoring --all enable. That's very funny, WDYT @yp969803

[yp969803]

raised a pr for this