wu-sheng opened a new issue, #9832: URL: https://github.com/apache/skywalking/issues/9832
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/skywalking/issues?q=is%3Aissue) and found no similar issues. ### Apache SkyWalking Component OAP server (apache/skywalking) ### What happened We noticed an Envoy bug reported through https://github.com/envoyproxy/envoy/issues/23579. Generally, this is caused by ALS TCP didn't work as we expected, but only reported when TCP closed. So, the topology can't show TCP until TCP is closed, and metrics are wrong as the summary got statistics in the time point connection closed. ### What you expected to happen We expect the TCP ALS could report periodically, which should be fixed through https://github.com/envoyproxy/envoy/pull/23630 by @wbpcode (Thank you) ### How to reproduce Just observe TCP traffic in Istio mesh ### Anything else SkyWalking backend should do several things to adopt this fix, - A new TCP-specific mesh object(ref https://github.com/apache/skywalking-data-collect-protocol/blob/3dc973f859e4dab9521bac7f5d2ede2c4f57c524/service-mesh-probe/service-mesh.proto#L36) should be added. - Add TCP-specific sources(service, instance, service relation, and instance relation), which are only generated from TCP-specific mesh object - Metrics in the TCP ALS are counters from the TCP connection established(confirmed by @wbpcode), so we need to build an incrementing mechanism compared to the last report(same pod), and then push the data into the sources for OAL engine. @mrproliu Could you confirm, the ALS route in Satellite is service instance oriented? So one service pod's ALS could be sent to a certain OAP backend. I hope we could fix this in 9.3.0, of course, this only means the changes on SkyWalking side should be done. Envoy has its roadmap, and we should mention this fix(Envoy fix) in docs and change logs to indicate the fixed version. ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
