-
Notifications
You must be signed in to change notification settings - Fork 4
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
How can I visualize the graph? #4
Comments
This part of the tool is not ready yet. The tweet was "just" a sneak preview ;) I used the special output formatter JsonArangoGraphNodes Run the analyzer with the option Hence, I'm working on an own UI, but no documentation or anything available yet. You would need to try it yourself. I cannot support atm, because this is all in the prototype phase and things will change: Anyway, there is another output formatter JsonCytoscapeElements
You have to install and build the event-store-mgmt-ui: https://github.com/prooph/event-store-mgmt-ui If you get it to work and you can share the graph it would be nice if you provide me with an export so that I can import it on my machine and check your work ;) |
In the end I made a simple visualization using vis.js network. The one problem I have right now is that the JSON is missing information about which method on the aggregate root is called by which command handler. It's visible even in your example image - for example it's not clear that |
This information is currently only available when using the You could use the result of that formatter. It includes nodes and edges information that you can use as basis for other graph visualization tools as-well. |
@codeliner I saw your tweet about this tool and wanted to try it. I successfully generated a
prooph_message_flow.json
file for my project. Now I would like to turn it into the image like the one you had in your tweet. Can you give me some tips how to do it with arangodb? I saw your docker command in the tweet but I was unable to find thebin/arango_import_graph.php
file you used.The text was updated successfully, but these errors were encountered: