Event Lineage/Graph View

[Cali0707]

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.

[Cali0707]

cc @pierDipi Btw, the proposal is still WIP/not fully complete. I will continue working on it in the next few days, but feedback is much appreciated!

[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

[Cali0707]

@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.

[yijie-04]

/assign

[yijie-04]

/unassign

[github-actions[bot]]

This issue is stale because it has been open for 90 days with no activity. It will automatically close after 30 more days of inactivity. Reopen the issue with /reopen. Mark the issue as fresh by adding the comment /remove-lifecycle stale.

[Cali0707]

/remove-lifecycle stale /triage accepted