wu-sheng commented on a change in pull request #5800:
URL: https://github.com/apache/skywalking/pull/5800#discussion_r518443607
##########
File path: docs/en/setup/envoy/als_setting.md
##########
@@ -19,7 +19,7 @@ You need three steps to open ALS.
Note: SkyWalking OAP service is at skywalking namespace, and the port of
gRPC service is 11800
2. (Default is ACTIVATED) Activate SkyWalking [envoy
receiver](../backend/backend-receivers.md).
-3. Active ALS k8s-mesh analysis, set system env variable
`SW_ENVOY_METRIC_ALS_HTTP_ANALYSIS`=`k8s-mesh`
+3. Active ALS analyzer, there are two available analyzers, `k8s-mesh` and
`mx-mesh`, `k8s-mesh` will use the metadata from Kubernetes cluster, `mx-mesh`
will use the Envoy metadata exchange mechanism to get the service name, etc.,
set system env variable `SW_ENVOY_METRIC_ALS_HTTP_ANALYSIS=k8s-mesh`
Review comment:
```suggestion
3. Active ALS analyzer, there are two available analyzers, `k8s-mesh` and
`mx-mesh`, `k8s-mesh` uses the metadata from Kubernetes cluster, `mx-mesh` uses
the Envoy metadata exchange mechanism to get the service name, etc.. Setting
system env variable **SW_ENVOY_METRIC_ALS_HTTP_ANALYSIS** to activate the
analyzer, such as `SW_ENVOY_METRIC_ALS_HTTP_ANALYSIS=k8s-mesh`.
```
----------------------------------------------------------------
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]
