Problem:
Zipkin can consume the metrics sent but UI breaks when querying the data.
Solution:
The cluster name MUST to be defined on envoy's config context. If it's not, the span "span.localEndpoint.serviceName" is not generated and caused the UI to break.
Define it into the config file:
envoy.yaml: > node: id: foo cluster: foo static_resources: listeners: ...
Hi, for documentation purposes.
Problem: Zipkin can consume the metrics sent but UI breaks when querying the data.
Solution: The cluster name MUST to be defined on envoy's config context. If it's not, the span "span.localEndpoint.serviceName" is not generated and caused the UI to break.
Define it into the config file:
envoy.yaml: > node: id: foo cluster: foo static_resources: listeners: ...
or as init params:
envoy -c /etc/envoy.yaml --service-cluster ${NAME}
relates to: https://github.com/openzipkin/zipkin/issues/3072
Cheers,