istio: No destination workload labels when using fault injection

Bug description We’ve started using istios fault injection on chaos days at AutoTrader. However we’re then asking people to investigate their dashboards in order to understanding the cause of the faults they’re seeing, but none of them work as metrics reported with faults are missing workload labels.

EG:

app-a -> app-b = fine.

Add 10% 500 failure-rate to app-b

and destination_workload etc are unknown. Screenshot 2020-03-06 at 14 25 13

Expected behavior Workload labels to work with fault injection

Steps to reproduce the bug

Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm) 1.4.6

How was Istio installed?

Environment where bug was observed (cloud vendor, OS, etc)

About this issue

Original URL
State: open
Created 4 years ago
Reactions: 1
Comments: 19 (19 by maintainers)

Most upvoted comments

We have same issue. When using fault injection at multiple istio cluster, “destination_cluster” value is “unknown” too, so we cannot distinguish which cluster the destination service belongs to.

chinaran on Jan 5, 2023