-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: Topology map #6
Comments
I wonder if the same can be accomplished via a tracing dashboard UI, like Prometheus + Graphana. The topology can only be accomplished with tracing data, which (IMO) is a feature that belongs to something like Graphana. Thoughts on this? |
Kiali has topology map, Could we suggest Kiali support Dapr? |
Where does Kiali get its data from? |
Ok did some reading on this, looks like it's mostly tightly coupled with Istio. However - Kiali can read tracing data from Jaeger, and Jaeger can be set to work with Dapr via it's open telemetry collector: |
Well, Kiali gets its data from metrics, specifically, from Prometheus. The Prometheus query from Kiali is like But the metric from Dapr is not enough, for example,
There is no filed can extract Maybe we should redesign the metric like Before we modify metrics, we need to let Kiali list Dapr workloads(app, service, etc.). The Actions should be:
|
Kiali uses After that, Kiali can query Dapr graph from Prometheus. |
Hi,
this feature request came to my mind after yesterday's community call.
I think it would be helpful to include a graphical topology map that somehow visualizes the communication as well as dependencies between Dapr-enabled microservices. Maybe also some basic telemetry data.
I think this could be really helpful in bigger applications/environments and helps to gain insights and dependencies.
Greets Nico
The text was updated successfully, but these errors were encountered: