Skip to content

Proxy Based Stackdriver Telemetry

Pengyuan Bian edited this page Apr 7, 2020 · 11 revisions

Proxy Based Stackdriver Telemetry

From 1.4, Istio supports exporting Stackdriver telemetry (metrics, logs, and trace spans) directly from proxy instead of Mixer adapter.

Metrics and Log

To enable metrics and logs, add the following options into istioctl control plane configuration:

values:
  telemetry:
    enabled: true
    v2:
      enabled: true
      stackdriver:
        enabled: true
        logging: true

This will apply several EnvoyFilters to your cluster to enabled Metadata exchange filter and Stackdriver filter inside proxy.

Helm installation does not support these options, so alternatively you could generate the manifest with istioctl and extract out the configuration and apply them manually. Specifically run istioctl manifest generate with the aforementioned values, look for and apply versioned Stackdriver and Metadata Exchange EnvoyFilter, e.g. stackdriver-filter-1.5, metadata-exchange-1.5.

Trace

To enable tracing, set the following options in istioctl installation: --set values.global.enableTracing=true --set values.global.proxy.tracer=stackdriver. This will enable Envoy proxy to export traces directly to Stackdriver. You can adjust sampling rate using pilot.traceSampling option as other tracers.

Dev Environment

Writing Code

Pull Requests

Testing

Performance

Releases

Misc

Central Istiod

Security

Mixer

Pilot

Telemetry

Clone this wiki locally