-
Notifications
You must be signed in to change notification settings - Fork 577
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
Event Lineage/Graph View #7661
Comments
cc @pierDipi |
Adding this comment here as it's not directly related to the proposal, the underlying logic to create a navigable graph is interesting and it could become the basis for a more generic graph builder that is now being built for the backstage provider in https://github.com/knative-extensions/backstage-plugins, I believe we can start with having that as a library to be reused for different use cases |
@pierDipi agreed, if you are happy with the approach to building the graph that I outlined in the proposal I will start opening issues for that this week. Then we can continue on the proposal and refine where the graph view fits in with backstage, etc. |
/assign |
/unassign |
This issue is stale because it has been open for 90 days with no |
/remove-lifecycle stale |
Problem
Eventing provides APIs to build a loosely coupled, distributed system. This provides teams and services with high degrees of flexibility and autonomy, however it also makes the relations between services hard to understand as the number of services connected in the Event Mesh increases.
By providing a graph view of the "event lineage" we can enable users to understand their system and debug complex problems. Full proposal doc is here.
Persona:
Which persona is this feature for?
Administrators and developers
Exit Criteria
TODO
Time Estimate (optional):
How many developer-days do you think this may take to resolve? 30+
Additional context (optional)
Add any other context about the feature request here.
The text was updated successfully, but these errors were encountered: