Deploy this integration to send traces from your Istio service mesh layers to via the OpenTelemetry collector using logzio-otel-traces Helm chart.

Before you begin, you’ll need:

  • An applicaion instrumented by Istio in a Kubernetes cluster
  • Istioctl installed on your machine
  • An active account with

Configuration instructions

Deploy the Helm chart in the same Kubernetes cluster as your application

Add logzio-helm repo as follows:

helm repo add logzio-helm
helm repo update
Run the Helm deployment code
helm install  \
--set config.exporters.logzio.region=<<LOGZIO_ACCOUNT_REGION_CODE>> \
--set config.exporters.logzio.account_token=<<TRACING-SHIPPING-TOKEN>> \
logzio-otel-traces logzio-helm/logzio-otel-traces

Replace <<TRACING-SHIPPING-TOKEN>> with the token of the account you want to ship to.

If your account is hosted in any region other than us, replace LOGZIO_ACCOUNT_REGION_CODE> with the applicable region code.

Get the logzio-otel-traces service IP

Run kubectl get services and take a note of the IP address of the logzio-otel-traces service.

Set Istio to send traces to

Replace <<logzio-otel-traces-service-IP>> in the command below with the IP address obtained in the previous step and run the command.

istioctl install --set meshConfig.defaultConfig.tracing.zipkin.address=<<logzio-otel-traces-service-IP>>:9411 --set values.pilot.traceSampling=100.0

By default, we set the traceSampling to 100, which means that Istio will send 100% of the application traces to You can adjust this value as required.

Check for your traces

Give your traces some time to get from your system to ours, then open