[GitHub] [skywalking] XuejiaoZhang commented on issue #5394: Clarify the `Observe service mesh through ALS` steps in README

[GitBox]

XuejiaoZhang commented on issue #5394:
URL: https://github.com/apache/skywalking/issues/5394#issuecomment-682381036


   No luck with the approach we discussed, would anyone please demo/validate it?
   
   My testing in the following is based on Istio 1.7 and latest 
skywalking-kubenetes.
   
   1.  EnvoyAccessLog is enabled.
   <img width="909" alt="image" 
src="https://user-images.githubusercontent.com/18475917/91534001-67b1af00-e943-11ea-9e16-04aa50e7dfa2.png";>
   Also, access logs could be seen in the testing app called client here, 
access logs are also output to stout, we could see the following running 
`kubectl logs ...`
   <img width="965" alt="image" 
src="https://user-images.githubusercontent.com/18475917/91534352-f58d9a00-e943-11ea-9fb5-897ff7469cc2.png";>
   
   2. helm install skywalking with env variable  set 
SW_ENVOY_METRIC_ALS_HTTP_ANALYSIS = k8s-mesh.
   Run `kubectl exec` to login skywalking-oap pod 
   <img width="388" alt="image" 
src="https://user-images.githubusercontent.com/18475917/91534665-7c427700-e944-11ea-9a35-867fbb04eed9.png";>
   
   Issue: nothing showed on skywalking UI
   <img width="1244" alt="image" 
src="https://user-images.githubusercontent.com/18475917/91534591-59b05e00-e944-11ea-9890-8cf7de8e3f63.png";>
   
   Here are logs of skywalking-oap
   <img width="966" alt="image" 
src="https://user-images.githubusercontent.com/18475917/91534819-c9bee400-e944-11ea-88d4-f5ccfe1b3acb.png";>
   
   Any clue? Thanks.


----------------------------------------------------------------
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:
us...@infra.apache.org