Reputation: 1637
Is there any way in v0.8 to trace the istio objects that apply in a request.
Why the request has follow a specific path. For example it goes through the ingress -> gateway -> virtual service -> destination rule -> pod -> repeat...
And the applied rules in each object.
Thank you.
Upvotes: 0
Views: 178
Reputation: 93
There is a new project called Kiali that is built to achieve the goal of leveraging observability for service meshes. Kiali is based on Istio (they are working really close to istio community) and using always its latest version.
Kiali has a service graph where users can see which istio objects are applied to each service. Also, for each service, you can see more details of those istio objects.
I'll put here two screenshots as sneak peak:
Here the service list, where you can see that v3 and v2 nodes has a Circuit breaker (lightning symbol) and reviews service has a Virtual Service for routing request between v1 and v2. Note that the graph also shows health of all its services and connection between them.
From service graph, you can navigate to each service detail page where you can find, among other things, the definitions of its attached istio objects.
For more information about Kiali, check its webpage: kiali.io and its github: kiali/kiali
Upvotes: 1