search

backstage / community-plugins

Community plugins for Backstage
Apache License 2.0
139 stars 139 forks source link

[Plugin] RabbitMQ #260

Open O5ten opened 3 years ago

O5ten commented 3 years ago

Use Case

As a developer i want to see what exchanges, queues, bindings and consumers i have for a service in my RabbitMQ clusters.

Summary

I leave this issue here for myself as a reminder that we should shave away the internal assumptions from our internal RabbitMQ plugin and publish it as it can always make someone happy. These are all entities that do not require more than monitoring ACLs for a rabbitmq-user.

I'm thinking that matching on the entity names should be more than enough for MVP as a service can (and should) have a naming standard that allows you to understand which service is using a specific queue.

For example: x.my-squad.my-service.my-feature

   rabbitmq.com/match: 'my-team,my-queue,x.my-exchange'

Would yield these overviews per cluster where the cluster here named SIT

image

image

image

Project website (if applicable)

https://rabbitmq.com

Context

A message-broker is very much a part of many microservice architecture, whether it be Kafka, RabbitMQ or something else. And the more top-level information we can bring in the better.

O5ten commented 3 years ago

Forgot to assign myself. 😩

andrewthauer commented 3 years ago

@O5ten - Out of curiosity have you looked at AsynAPI as a way to document these? The existing API docs plugin supports AsyncAPI already and some of this information at least can be expressed using its spec.

O5ten commented 3 years ago

Neat! I have never heard of AsynAPI before but that would be really cool to implement as a part of this.

stale[bot] commented 3 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

nirga commented 3 years ago

Given that this hasn't been implemented yet, do we want to keep this open?

OrkoHunter commented 3 years ago

Yep!

github-actions[bot] commented 1 week ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.