[GitHub] [skywalking] Gitwangpin commented on issue #6762: skywalking monitoring envoy does not work

[GitBox <gi...@apache.org>]

Gitwangpin commented on issue #6762:
URL: https://github.com/apache/skywalking/issues/6762#issuecomment-820407280


   itstio config
   hub: docker.io/istio
     meshConfig:
       accessLogFile: /dev/stdout
       defaultConfig:
         envoyAccessLogService:
           address: 10.111.96.107:11800
         proxyMetadata: {}
       enableEnvoyAccessLogService: true
       enablePrometheusMerge: true
     profile: demo
     proxy:
       envoyMetricsService:
         enabled: true
     tag: 1.9.2
     
   skywalking config
     envoy-metric:
     selector: ${SW_ENVOY_METRIC:default}
     default:
       acceptMetricsService: ${SW_ENVOY_METRIC_SERVICE:true}
       alsHTTPAnalysis: ${SW_ENVOY_METRIC_ALS_HTTP_ANALYSIS:"k8s-mesh"}
       # `k8sServiceNameRule` allows you to customize the service name in ALS via Kubernetes metadata,
       # the available variables are `pod`, `service`, f.e., you can use `${service.metadata.name}-${pod.metadata.labels.version}`
       # to append the version number to the service name.
       # Be careful, when using environment variables to pass this configuration, use single quotes(`''`) to avoid it being evaluated by the shell.
       k8sServiceNameRule: ${K8S_SERVICE_NAME_RULE:"${service.metadata.name}"}
   
   I checked and found that I turned on metrics service.
   


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