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

[Idea] Consider using flower for celery monitoring #291

Open
se7entyse7en opened this issue Sep 27, 2019 · 3 comments
Open

[Idea] Consider using flower for celery monitoring #291

se7entyse7en opened this issue Sep 27, 2019 · 3 comments
Labels
enhancement New feature or request needs discussion/agreement This issue needs some discussion or agreement triage/needs-product-input This needs input from product

Comments

@se7entyse7en
Copy link
Contributor

se7entyse7en commented Sep 27, 2019

See link.

As we verified with the demos/pocs celery is an important part of the application that IMO should be monitored. Flower provides a webapp based tool for monitoring and administrating celery. It seems to also provide an http api to expose the functionalities.

As an idea related to this, we could also explore checking the status of the celery queue and eventually manage, increase or restart the worker pool for example. In the last demo, for example, a restart of the celery workers would have helped, maybe there's a chance we could automate as well this kind of issues.

@carlosms carlosms added the triage/needs-product-input This needs input from product label Sep 27, 2019
@rpau
Copy link

rpau commented Sep 27, 2019 via email

@smacker
Copy link
Contributor

smacker commented Sep 27, 2019

Yep. I would prefer to use Prometheus to track all the metrics in the same place (celery, webserver, db, cache, bblfsh, ...).

@se7entyse7en
Copy link
Contributor Author

se7entyse7en commented Sep 27, 2019

Sure! If we can use it and also extend it to have a centralized view of all the services it would be great!

@se7entyse7en se7entyse7en added enhancement New feature or request needs discussion/agreement This issue needs some discussion or agreement labels Oct 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request needs discussion/agreement This issue needs some discussion or agreement triage/needs-product-input This needs input from product
Projects
None yet
Development

No branches or pull requests

4 participants