rabbitmq-queue-dashboard: fixed an issue with the usage of the datasource, added meaningful Legends and refresh to 10s

[sherifkayad]

rabbitmq-queue-dashboard: fixed an issue with the usage of the datasource, added meaningful Legends and refresh to 10s

This closes #

Note to reviewers: remember to look at the commits in this PR and consider if they can be squashed

Summary Of Changes

rabbitmq-queue-dashboard:

• fixed an issue with the usage of the datasource
• added meaningful Legends
• added refresh to 10s

Additional Context

Local Testing

Please ensure you run the unit, integration and system tests before approving the PR.

To run the unit and integration tests:

$ make unit-tests integration-tests

You will need to target a k8s cluster and have the operator deployed for running the system tests.

For example, for a Kubernetes context named dev-bunny:

$ kubectx dev-bunny
$ make destroy deploy-dev
# wait for operator to be deployed
$ make system-tests

[sherifkayad]

@DanielePalaia can you please have a look at that one as well? 😉 thanks in advance

[DanielePalaia]

Hi @sherifkayad Thank you for the PR. Just to help us on the review, could you explain what issue you are experimenting with this dashboard and what improvements are you bring in? (Maybe also opening an issue and link it to this PR would be nice, and why not posting the grafana images if possibile).

[sherifkayad]

@DanielePalaia The issue I had was if one would have a Prometheus DS not with the name Prometheus then this Dashboard would break; so I fixed that.

In addition, I added some legends to the Graph such that one could understand which value (bar) is the messages and which is the consumers.

My bad I didn't add some screenshots .. There you go.

[Zerpet]

Tried out the changes in this PR. This is the before:

And after:

[Zerpet]

Thank you!

[sherifkayad]

@Zerpet thanks for the feedback .. glad to be able to contribute something to this awesome repo!