<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Jay Shaughnessy on Medium]]></title>
        <description><![CDATA[Stories by Jay Shaughnessy on Medium]]></description>
        <link>https://medium.com/@jshaughn?source=rss-48eec6e5725d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Af4HxoObPAHShKimqOCt8A.jpeg</url>
            <title>Stories by Jay Shaughnessy on Medium</title>
            <link>https://medium.com/@jshaughn?source=rss-48eec6e5725d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 22:53:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jshaughn/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Kiali 2.0 for Istio]]></title>
            <link>https://medium.com/kialiproject/kiali-2-0-for-istio-2087810f337e?source=rss-48eec6e5725d------2</link>
            <guid isPermaLink="false">https://medium.com/p/2087810f337e</guid>
            <category><![CDATA[openshift]]></category>
            <category><![CDATA[observability]]></category>
            <category><![CDATA[istio-service-mesh]]></category>
            <category><![CDATA[kiali]]></category>
            <category><![CDATA[patternfly]]></category>
            <dc:creator><![CDATA[Jay Shaughnessy]]></dc:creator>
            <pubDate>Mon, 21 Oct 2024 14:43:05 GMT</pubDate>
            <atom:updated>2024-10-21T14:43:05.612Z</atom:updated>
            <content:encoded><![CDATA[<p>It’s been seven+ years and Istio Service Mesh is still on the rise. And for nearly as long the Kiali project has been developed alongside, to supply a world class console for Istio. Istio continues to evolve and so we’ve decided that now is the right time, with Istio Ambient emerging, to make a major version change. So, let me introduce a few key changes for Kiali 2.0.</p><h3><strong>Configuration</strong></h3><p>Important changes in the Kiali CR.</p><p><strong>Discovery Selectors</strong></p><p>If you have configured Kiali then you are likely aware of our fairly complex way of defining “Accessible Namespaces”. The set of namespaces that Kiali knows about and can present to the user, is currently the result of all of these settings:</p><ul><li>deployment.accessible_namespaces</li><li>api.namespaces.exclude</li><li>api.namespaces.include</li><li>api.namespaces.label_selector_exclude</li><li>api.namespaces.label_selector_include</li></ul><p>Getting it right, including things like regex expressions, could be daunting. In Kiali 2.0 they have all been retired in favor of the same mechanism used by Istio to limit namespace scope: Discovery Selectors. And by the way, if you don’t use these in Istio then you may want to, it can narrow what the control plane has to do. In short, these are Kubernetes Label Selectors that define the set of namespaces, based on labels, that Kiali will care about.</p><p>NOTE: If you have customized Kiali’s accessible namespaces in 1.x, then this is a breaking change and you will need to update configuration when updating to Kiali 2.x.</p><p>For more details, see <a href="https://kiali.io/docs/configuration/namespace-management/">Namespace Management</a> on kiali.io.</p><p><strong>External Service URLs</strong></p><p>Another configuration pain point has been how to define the URLs for Kiali’s Grafana and Tracing external services. In Kiali 2.0 we’ve deprecated:</p><ul><li>external_service.grafana.in_cluster_url</li><li>external_service.grafana.url</li><li>external_service.tracing.in_cluster_url</li><li>external_service.tracing.url</li></ul><p>And renamed them to:</p><ul><li>external_service.grafana.internal_url</li><li>external_service.grafana.external_url</li><li>external_service.tracing.internal_url</li><li>external_service.tracing.external_url</li></ul><h3>The Traffic Graph</h3><p>Undoubtedly one of Kiali’s key features, the traffic graph has gotten a face lift.</p><p><strong>PatternFly Topology (PFT)</strong></p><p>Kiali has always been written using PatternFly UI components. But when Kiali originated, PatternFly did not have a Topology component. And so we successfully implemented the graph using Cytoscape. Cytoscape has been great, but it has not been seamless to have a large non-PatternFly component embedded inside Kiali. We’ve been waiting for PFT to mature, and we believe it’s now ready to take over as our default graph implementation. It’s got a more modern look and feel, and has really nice support for dark mode:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qVku2BTeverIOhd1q2TIJQ.png" /></figure><p>We really hope you like it, but for those with separation issues the Cytoscape graph will still be available via configuration option, although deprecated.</p><p><strong>Istio Ambient</strong></p><p>With the upcoming release of Istio v1.24, Istio Ambient will likely start seeing more robust use. Ambient presents some challenges to the traffic graph visualization. There are two major reporters of traffic telemetry: ztunnel and waypoints. TCP/L4 telemetry is reported by ztunnel, and unlike sidecar telemetry, which reported protocol-specific telemetry, ztunnel reports for all traffic. Waypoints (which are proxies) report HTTP/L7 telemetry. Furthermore, for an HTTP request from A-&gt;B, the waypoint (WP) will report the A-&gt;B traffic, but ztunnel will also report A-&gt;WP and WP-&gt;B. The end result is that it’s easier than ever to have a very busy graph, even for a fairly simple mesh, and especially if you want to peek into the Ambient infrastructure. In Kiali 2.0 the Traffic Dropdown lets you control what you see related to Ambient</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/182/1*06bJVt5j6uUD0qKFxSbxig.png" /></figure><p>For example, by selecting only Waypoint Ambient telemetry, you can get a Bookinfo graph that looks pretty similar to your classic sidecar graph:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/754/1*HlWCyhCMvFo9D0W_3MKIRw.png" /></figure><p>But as shown in the dropdown image above, you could also select only ztunnel Ambient telemetry. This, combined with the new Show Waypoints feature in the Display menu, gives you a good look at the ztunnel-waypoint interaction:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*APs4RfhapJH0SLQiPA-R0A.png" /></figure><p>Note that non-Ambient proxy telemetry, like the gateway above, still shows up and gives us the HTTP edges from the gateway to productpage-v1 app.</p><p>One more feature you may notice above is that some of edges involving the waypoint are now bi-directional. This is to simplify waypoint graphing, because there is often to/from ztunnel traffic between the waypoint and another node:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*z38MzqlKZn57L4YZBJJuJg.png" /></figure><p>Note the side-panel allows you to easily swap the edge direction, when selected.</p><p>For more details see <a href="https://kiali.io/docs/features/ambient/">Istio Ambient Mesh</a> on kiali.io.</p><h3>The Mesh Graph</h3><p>Although not brand new in Kiali 2.0, the Mesh page has been recently introduced, and has been upgraded quickly, with a lot of hardening and multi-cluster support additions for v2.0.</p><p>Savvy Kiali users may have already noticed the use of PatternFly Topology for this new mesh visualization. For those that have yet to see it, this page aims to complement the Traffic Graph. Where the Traffic Graph shows the requests flowing through the mesh, this topology shows your mesh infrastructure: Istiod control planes, data planes, Kiali instances, and other Add-On components. You can view configuration, versions, health, relationships, various metrics, etc. There is multi-cluster support and also views into revisions and canary-upgrades:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AY4d_b3C_IjCfZy1-O-wnw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/876/1*n8XBGkbiO1A2FHrDwO9OHQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/837/1*aP4u269NVUNcEeTEGiW_ug.png" /></figure><p>We’ll be rolling out more features into the mesh page, if you have ideas about what you’d like it to do, please drop us a note.</p><h3>And More…</h3><p>Those are the heavy hitters in Kiali 2.0. But of course there’s plenty more:</p><ul><li>Performance and scale improvements</li><li>Multi-cluster deployment model enhancements</li><li>Gateway API 1.2 support</li><li>Improved Tempo support</li><li><a href="https://github.com/kiali/kiali/blob/master/design/KEPS/extensions/proposal.md">Kiali Extension support</a></li><li>Partial Chinese localization</li><li>And a bunch of important fixes</li></ul><h3>Istio on Red Hat OpenShift…</h3><p>Kiali is an open source project and our goal is to improve the experience of all Istio users. But considering that all of the full time Kiali maintainers work for Red Hat, we also hope you’ll consider Istio on Red Hat OpenShift. OpenShift includes OpenShift Service Mesh (OSSM), a fully supported Istio distribution, and OSSM 3.0 will be out soon. It also includes supported versions of Kiali and OSSMC, the Kiali-powered OpenShift plugin, which is also better than ever with Kiali 2.0:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zOgyXijPyOVpBOja.png" /><figcaption>OSSM Console Plugin</figcaption></figure><p>Thanks for using Istio with Kiali. If you have questions or ideas please find us on the <a href="http://istio.slack.com/">Istio Slack</a> #kiali channel, or open a discussion at <a href="https://github.com/kiali/kiali">Kiali Github</a>. And if you have the desire, we would love to have you as a contributor, or even as a maintainer!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2087810f337e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/kialiproject/kiali-2-0-for-istio-2087810f337e">Kiali 2.0 for Istio</a> was originally published in <a href="https://medium.com/kialiproject">Kiali</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kiali Mid-Sprint Bonus — Response Flags]]></title>
            <link>https://medium.com/kialiproject/kiali-mid-sprint-bonus-response-flags-4260cc8a2580?source=rss-48eec6e5725d------2</link>
            <guid isPermaLink="false">https://medium.com/p/4260cc8a2580</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[openshift]]></category>
            <category><![CDATA[kiali]]></category>
            <category><![CDATA[istio]]></category>
            <category><![CDATA[service-mesh]]></category>
            <dc:creator><![CDATA[Jay Shaughnessy]]></dc:creator>
            <pubDate>Wed, 27 Mar 2019 13:55:15 GMT</pubDate>
            <atom:updated>2019-03-27T14:16:41.817Z</atom:updated>
            <content:encoded><![CDATA[<h3>Kiali Mid-Sprint Bonus — Response Flags</h3><p>A nice little feature is included in sprint 20 for the <a href="http://kiali.io/">Kiali project</a>. Kiali is a project for observing your <a href="https://istio.io/">Istio service mesh</a> on OpenShift or Kubernetes. Kiali is observability for Istio, and we try hard to give you the very best graph visualization of your service topology. The graph helps you confirm that your mesh is behaving well, or to quickly identify areas that may need attention. For example, using the common <em>bookinfo </em>example, we can see below that requests from productpage to the details service are having issues:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dAXMQj6r4mrA1GExo5VAPA.png" /><figcaption>Bookinfo Namespace Graph</figcaption></figure><p>The red edge indicates failures and the summary panel on the right reflects failures as well. Currently the summary is for the entire bookinfo namespace because we have not selected any graph element. Let’s focus on the problem edge by zooming in and clicking it:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X6geyBfoUp-gtIRX8w-Isw.png" /><figcaption>Select the Problem Edge</figcaption></figure><p>Now the side panel summarizes the edge from the productpage app to the details service. We pause the graph and see that for the current time period we’re making about 1 request per second and that about 17% of the requests are failing. We can also see that the details service is decorated with an Istio virtual service (the “fork” badge on the node label shows this). But we still don’t know exactly why the requests are failing. To find out we can turn to the new <strong>Response Flags </strong>tab in the side panel. You’ll notice that there are now two tabs in the edge summary panel: <em>Traffic</em> and <em>Response Codes</em>. The default <em>Traffic</em> tab provides the familiar table and bar chart summary of the request traffic. Now let’s click on the new <em>Response Codes</em> tab:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/317/1*L2tFL_x_Gsmx6L-ssI0n2w.png" /><figcaption>Response Codes Tab</figcaption></figure><p>This new table provides the actual response codes reported for the current time period, broken down by any provided response flags. By hovering we can get a description of the code. We can now see that the failures are being generated by fault injection (FI) due to the virtual service. There are several response flags to help understand your traffic, here are a just a few that can be very useful:</p><ul><li>DC (downstream connection failure)</li><li>FI (fault injection)</li><li>UO (overflow/open circuit breaker)</li><li>UT (upstream request timeout)</li></ul><p>From here we can do more cool stuff, all inside Kiali, like navigate to the service detail, edit the virtual service yaml and change the FI rate, or get lots of more detailed charts about historical performance, etc. We push a new <a href="https://hub.docker.com/r/kiali/kiali">docker release</a> at the end of every sprint, and update the latest tag on every merge to master, so keep an eye out for this new feature.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4260cc8a2580" width="1" height="1" alt=""><hr><p><a href="https://medium.com/kialiproject/kiali-mid-sprint-bonus-response-flags-4260cc8a2580">Kiali Mid-Sprint Bonus — Response Flags</a> was originally published in <a href="https://medium.com/kialiproject">Kiali</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kiali Mid-Sprint Bonus — Graph Find]]></title>
            <link>https://medium.com/kialiproject/kiali-mid-sprint-bonus-graph-find-119f35479c6e?source=rss-48eec6e5725d------2</link>
            <guid isPermaLink="false">https://medium.com/p/119f35479c6e</guid>
            <category><![CDATA[kiali]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[istio]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[openshift]]></category>
            <dc:creator><![CDATA[Jay Shaughnessy]]></dc:creator>
            <pubDate>Mon, 14 Jan 2019 14:54:06 GMT</pubDate>
            <atom:updated>2019-01-14T14:54:06.953Z</atom:updated>
            <content:encoded><![CDATA[<h3>Kiali Mid-Sprint Bonus — Graph Find</h3><p>We’re in the middle of sprint 16 for the <a href="http://kiali.io/">Kiali project</a> and it’s going well. Kiali is a project for observing your Istio service mesh on Kubernetes or OpenShift. We continue to try and provide the best graph visualization possible. In the last several sprints we have added great stuff like detailed node graphs (drill down with double-click), service-entry nodes, and multi-namespace support. But today I want to let you know about the new <strong>Graph Find</strong> feature, just merged into <a href="https://github.com/kiali/kiali">master</a> a few days ago. Graph Find is a powerful new way to locate and highlight items of interest in the graph. You’ll see a new text box that let’s you type in a variety of simple criteria. It looks like this, and if you click the help icon you’ll get a bunch of help on how to use it:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/284/1*XArI6N5C46BdoWWILSEnGA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k3Pn6loEIyCyur2siAXnow.png" /></figure><p>I’ll just run through a few examples. Sometimes, when you have a larger mesh displayed it’s hard to locate a specific node because of the zoom level. In the example below I want locate nodes related to my <em>productpage</em> service. I enter, “name = productpage”:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qGCjLy1Iw5qF92SDEOABHw.png" /></figure><p>I can quickly see the four highlighted nodes and zoom in as needed. Note that there are lot of operators available: contains, startswith, not, etc. There are also a bunch of operands. Graph Find also supports AND and OR. In the following example I want to find my virtual services in the <em>bookinfo</em> namespace. I could type in “namespace = bookinfo AND has virtualservice”. But I’m going to shorten things a bit to demonstrate that as you learn the query language it can be a bit less verbose. I’ll type in “ns *= book and vs”:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RtLr_FdTWwYs9AH1k2sfoQ.png" /></figure><p>I can see that there is one highlighted virtual service node.</p><p>I can can also find edges of interest. For example, let’s identify edges with a response time &gt; 50ms. I enable response time edge labels and then type in “responseTime &gt; 50”:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SfRA0ehgHc8Se8ntTPxx5Q.png" /></figure><p>Note that the Find re-evaluates each time the graph updates, so if I sit back and watch with auto-refresh, the highlighted edges can change on each update.</p><p>The new Graph Find feature helps you quickly identify items of interest in the graph. Let us know what you think.</p><p>I didn’t show it explicitly, but if you look closely at the screenshots above (see the top left selector, and also the summary panel to the right) you’ll notice the multi-namespace feature; I had three specific namespaces included in my graph. That’s just one of many recent additions in Kiali. If you are using Istio you should also be using Kiali for observation. And of course, Kiali is always looking for feedback and contributors! For help getting started visit the <a href="http://kiali.io/">Kiali homepage</a> or <a href="https://github.com/kiali/kiali">Kiali on Github</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=119f35479c6e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/kialiproject/kiali-mid-sprint-bonus-graph-find-119f35479c6e">Kiali Mid-Sprint Bonus — Graph Find</a> was originally published in <a href="https://medium.com/kialiproject">Kiali</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kiali Mid-Sprint Bonus — Service Graph]]></title>
            <link>https://medium.com/kialiproject/kiali-mid-sprint-bonus-service-graph-1f8cc5f877cf?source=rss-48eec6e5725d------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f8cc5f877cf</guid>
            <category><![CDATA[kiali]]></category>
            <category><![CDATA[istio]]></category>
            <category><![CDATA[openshift]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[service-mesh]]></category>
            <dc:creator><![CDATA[Jay Shaughnessy]]></dc:creator>
            <pubDate>Tue, 02 Oct 2018 14:03:58 GMT</pubDate>
            <atom:updated>2018-10-02T14:03:58.290Z</atom:updated>
            <content:encoded><![CDATA[<p>We’re in the middle of sprint 12 for the <a href="http://kiali.io/">Kiali project</a> and it’s going well. Kiali is a project for observing your Istio-based service meshes on Kubernetes or OpenShift. In the last several sprints we have done a lot of cool stuff with the graph, adding new graph types, service injection, and lots of work to improve the user experience. I’m not going to go into all of it because Mazz already has a <a href="https://medium.com/kialiproject/different-mesh-visualizations-in-kiali-82a3428ae155?source=search_post---------3">nice blog for you to check out</a>. But just added yesterday into <a href="https://github.com/kiali/kiali">master</a> is a new graph type, the <strong>Service Graph</strong>. Whereas the workload graph gives you your most physical view of the mesh, the service graph gives you your most logical view of the mesh. Let’s look at a workload graph first. It gives you something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YxJtBwc43PQEzCH8R2m6Kg.jpeg" /><figcaption>Workload graph type</figcaption></figure><p>In Istio requests flow from workload to workload. An Istio workload on Kubernetes or OpenShift is typically a deployment (although it can be other things, like a replica-set). Each workload can handle multiple services. The circle nodes represent workloads. Triangles represent services. In this graph we see only one triangle, it is showing that some requests for the <em>details </em>service failed before reaching a workload (because of an Istio fault injection rule I have set up for testing).</p><p>We can toggle on the <em>Show Services </em>option in the <em>Display</em> drop-down and we’ll be able to see the requested services and how they get directed to a workload for handling:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*skRXYYI1cPBEENSygCLH7w.jpeg" /><figcaption>Workload graph type with show services option</figcaption></figure><p>Now we can see lots of triangles injected between the workloads. This shows us the requested services and then how those service requests were directed (after applying virtual service rules in Istio). This is great but we’ve also had requests for a pure service graph. App developers think about services requesting services. The workloads show the mechanics of how the service interaction is actually happening, but it can be useful to see the logical service interaction as well. By selecting the new <strong>Service graph type</strong>, we get the following:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jw3DZoAxKK7x5vcwi3gjdw.jpeg" /></figure><p>With the service graph type we can see the request traffic between our services, with traffic aggregated as necessary to best see the logical app design and the actual request flow.</p><p>There have been a ton of other great recent additions in Kiali. If you are using Istio you should also be using Kiali for observation. And of course, Kiali is always looking for feedback and contributors! For help getting started visit the <a href="http://kiali.io/">Kiali homepage</a> or <a href="https://github.com/kiali/kiali">Kiali on Github</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f8cc5f877cf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/kialiproject/kiali-mid-sprint-bonus-service-graph-1f8cc5f877cf">Kiali Mid-Sprint Bonus — Service Graph</a> was originally published in <a href="https://medium.com/kialiproject">Kiali</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kiali Mid-Sprint Bonus — Multi-Mesh Service Graph]]></title>
            <link>https://medium.com/kialiproject/kiali-mid-sprint-bonus-multi-mesh-service-graph-87961c370ad6?source=rss-48eec6e5725d------2</link>
            <guid isPermaLink="false">https://medium.com/p/87961c370ad6</guid>
            <category><![CDATA[istio]]></category>
            <category><![CDATA[kiali]]></category>
            <category><![CDATA[microservices]]></category>
            <dc:creator><![CDATA[Jay Shaughnessy]]></dc:creator>
            <pubDate>Wed, 06 Jun 2018 18:18:49 GMT</pubDate>
            <atom:updated>2018-06-06T18:18:49.430Z</atom:updated>
            <content:encoded><![CDATA[<p>Kiali Mid-Sprint Bonus — Multi-Mesh Service Graph</p><p>We’re in the middle of sprint 6 for the<a href="https://kiali.org/"> Kiali project </a>and it’s going well. Kiali is a project for observing your Istio-based service meshes on Kubernetes or OpenShift. One thing users have been asking for is the ability to view multiple service meshes in one combined graph. We’ve updated things to make the default service graph view show all your meshes together, and then you can drill down into a specific namespace as desired. Here’s an example of a combined mesh with one mesh highlighted…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P7FdZX7tvfI78M9pCuR1CQ.jpeg" /></figure><p>We can drill down into that mesh and take a closer look…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BSQotewq8uaTyZTCcxd06w.jpeg" /></figure><p>And once we’ve located a service we’re really interested in we can drill into it’s full detail view via the link in the summary to the right…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qFPqBHZ-8UcyPkioHpe_kA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4ykP65r7ObKdALdn2Dpubg.jpeg" /></figure><p>With Kiali you can quickly observe your mesh, locate, investigate and solve issues. For help getting started visit the<a href="https://kiali.org/"> Kiali homepage</a> or <a href="https://github.com/kiali/kiali">Kiali on Github</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=87961c370ad6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/kialiproject/kiali-mid-sprint-bonus-multi-mesh-service-graph-87961c370ad6">Kiali Mid-Sprint Bonus — Multi-Mesh Service Graph</a> was originally published in <a href="https://medium.com/kialiproject">Kiali</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>