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
Bug description
When two pods with '.' in their names are injected sidecars and then make http request from one to another, the generated mixer data is missing some fields which depends on pod info, which includes:
source/destination.labels
source/destination.name
source/destination.owner
source/destination.workload
destination.namespace (parsed as default but it's wrong)
When making a request from a.deploy.powerful-mix to b.deploy.powerful-mix, we can't get information of this request from prometheus or kiali, and the access log on istio-telemetry is:
Bug description
When two pods with '.' in their names are injected sidecars and then make http request from one to another, the generated mixer data is missing some fields which depends on pod info, which includes:
default
but it's wrong)When making a request from
a.deploy.powerful-mix
tob.deploy.powerful-mix
, we can't get information of this request from prometheus or kiali, and the access log on istio-telemetry is:The json is formatted as:
As we know, the default logentry config shows mappings of the fields:
So we can infer the above attributes are missing or incorrectly parsed.
Expected behavior
The mixer access log should show the right information of source workload and destination workload.
And we should be able to see this request on kiali and prometheus.
Steps to reproduce the bug
a.deploy
andb.deploy
a.deploy-xxx-xxx
tob.deploy-xxx-xxx
Version (include the output of
istioctl version --remote
andkubectl version
andhelm version
if you used Helm)1.3.x
How was Istio installed?
installed with config for mixer:
Environment where bug was observed (cloud vendor, OS, etc)
Linux
The text was updated successfully, but these errors were encountered: