wu-sheng commented on a change in pull request #6727: URL: https://github.com/apache/skywalking/pull/6727#discussion_r627470736
########## File path: docs/en/setup/envoy/als_setting.md ########## @@ -29,8 +29,9 @@ On Istio version 1.6.0+, if Istio is installed with [`demo` profile](https://ist - Activate SkyWalking [Envoy Receiver](../backend/backend-receivers.md). This is activated by default. -- Choose an ALS analyzer. There are two available analyzers, `k8s-mesh` and `mx-mesh`. - Set the system environment variable **SW_ENVOY_METRIC_ALS_HTTP_ANALYSIS** such as `SW_ENVOY_METRIC_ALS_HTTP_ANALYSIS=k8s-mesh` +- Choose an ALS analyzer. There are two available analyzers, `k8s-mesh` and `mx-mesh` for both HTTP access logs and TCP access logs. + Set the system environment variable **SW_ENVOY_METRIC_ALS_HTTP_ANALYSIS** and **SW_ENVOY_METRIC_ALS_TCP_ANALYSIS** + such as `SW_ENVOY_METRIC_ALS_HTTP_ANALYSIS=k8s-mesh`, `SW_ENVOY_METRIC_ALS_TCP_ANALYSIS=k8s-mesh` Review comment: That is strange, and doesn't make sense. Could you look deeper to see what is really happening? Such as why TCP topology could be generated from both sides? Especially server side's ALS, what does it look like? -- 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. For queries about this service, please contact Infrastructure at: [email protected]
