You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to firstly thank you all for the hard works, it save me a lot of time to construct a microservice sample application. I was trying out deploying the monitoring stack on a on-premise k8s cluster. I found that jaeger is not working out of the box after followed through the manual. No trace data was showing in the jaeger dashboard. I use the following config file for istioctl and solve the problem by adding the meshConfig.defaultConfig.tracing.zipkin.addressfield:
Above script needs to add istioctl in the uBench docker image. I guess Istioctl is a good tool to have in the uBench image for managing istio lifecycle. If adding istioctl to the uBench image is not perfered, adding above configuration in the istio helm chart will also be a choice.
The text was updated successfully, but these errors were encountered:
Hi team,
I would like to firstly thank you all for the hard works, it save me a lot of time to construct a microservice sample application. I was trying out deploying the monitoring stack on a on-premise k8s cluster. I found that jaeger is not working out of the box after followed through the manual. No trace data was showing in the jaeger dashboard. I use the following config file for istioctl and solve the problem by adding the
meshConfig.defaultConfig.tracing.zipkin.address
field:The install script that uses istioctl for installation will be:
Above script needs to add istioctl in the uBench docker image. I guess Istioctl is a good tool to have in the uBench image for managing istio lifecycle. If adding istioctl to the uBench image is not perfered, adding above configuration in the istio helm chart will also be a choice.
The text was updated successfully, but these errors were encountered: