Skip to content
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

Visualizing topics/queues instead of just schemas #449

Open
1 task done
skonik opened this issue Oct 2, 2023 · 7 comments
Open
1 task done

Visualizing topics/queues instead of just schemas #449

skonik opened this issue Oct 2, 2023 · 7 comments

Comments

@skonik
Copy link

skonik commented Oct 2, 2023

Have you read the Contributing Guidelines on issues?

Description

Hello, is it possible to add some kind of topic/queue name link which can affect visualization?
Everything looks great with just events, but sometimes I need to understand what kafka topics are connected.
Would be nice to have such feature.

Motivation

To be able track connections between topics/queues instead of just events.

@GDS-Dominic
Copy link

GDS-Dominic commented Dec 13, 2023

Not necessarily just topics / queues. There could be some sort of service which routes events do other consumers

@gongshishao
Copy link

Any update ?

@boyney123
Copy link
Owner

Love this idea!

@boyney123
Copy link
Owner

Do you have any ideas on how this would look?

@skonik
Copy link
Author

skonik commented Apr 14, 2024

Would be enough to provide an option "All queues and services " as second option. Just change events to queues/topics and that's exactly what I would like to see.

Screenshot 2024-04-14 at 15 54 20

In next iteration it might be cool to create a tooltip on queue node showing a list of events connected to queue.

@boyney123
Copy link
Owner

@skonik curious what you think about having channels as a entity in the catalog. You will be able to create them like you can events, document them and link them between things.

Topics, maybe the ability to change the name of the event (type: topic) or something may work, or just accept topics as an entity too?

@skonik
Copy link
Author

skonik commented Apr 16, 2024

@skonik curious what you think about having channels as a entity in the catalog. You will be able to create them like you can events, document them and link them between things.

Introducing channels is good idea. Concept of channels is being described by asyncapi specification. It could be used as reference

Topics, maybe the ability to change the name of the event (type: topic) or something may work, or just accept topics as an entity too?

We should go with channel as new entity and display channel name as node label then.
So, not topics, but channels with specified name, I guess.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants