-
Notifications
You must be signed in to change notification settings - Fork 235
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
Whats the best approach to monitor queues in microservices. #308
Comments
@zebkailash I personally use a shared redis instance for multiple apps/services and I use different queues for differnet topics. That way you can point arena to a single redis instance and monitor all queues. If there is a special reason to have multiple redis instances, you can also configure a single arena instance to connect to both redis servers. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
How should we monitor queues lets say we have 2 Microservices MS1, MS2 each have their own Redis instance and each service pushes the job to their respective Redis instance. There is another service let's say admin service which will like to monitor all these queues. How should this be implemented? Should the admin service directly provide the configuration details of different redis instances?
The text was updated successfully, but these errors were encountered: