You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 18, 2024. It is now read-only.
To develop the CDEvents specification we build proof of concepts and run demos that connect multiple tools together via CDEvents. During the demos it's often challenging to visualise the progress and overall flow of events because of the distributed nature of event based architectures.
It would be useful to build a front end tool to visualise the CDEvents sent over time, and their relations.
The tools would pull the events from some kind a storage (e.g. a document storage, object storage or else), allow filtering of events based on CDEvent fields, and it would allow displaying connections between events based on customisable CDEvents fields.
The solution should aim for the smallest possible footprint, so that it may be run on a user laptop along with the rest of the demo.
The tool can be a proof of concept itself to start with, and may evolve over time based on the CDEvents project needs.
The text was updated successfully, but these errors were encountered:
To develop the CDEvents specification we build proof of concepts and run demos that connect multiple tools together via CDEvents. During the demos it's often challenging to visualise the progress and overall flow of events because of the distributed nature of event based architectures.
It would be useful to build a front end tool to visualise the CDEvents sent over time, and their relations.
The tools would pull the events from some kind a storage (e.g. a document storage, object storage or else), allow filtering of events based on CDEvent fields, and it would allow displaying connections between events based on customisable CDEvents fields.
The solution should aim for the smallest possible footprint, so that it may be run on a user laptop along with the rest of the demo.
The tool can be a proof of concept itself to start with, and may evolve over time based on the CDEvents project needs.
The text was updated successfully, but these errors were encountered: