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

Alert on App Panel when Celery Server is Down #410

Open
3 tasks
kc-diabeat opened this issue Nov 12, 2024 · 2 comments
Open
3 tasks

Alert on App Panel when Celery Server is Down #410

kc-diabeat opened this issue Nov 12, 2024 · 2 comments
Labels

Comments

@kc-diabeat
Copy link
Contributor

Background:
App Panel relies on Celery server for processing a number of necessary tasks (e.g. App Launch), and if the Celery server is down, it can affect the usability of the App Panel as well as the developer application that might have packages relying on Celery for background jobs.

Proposed Solution:

  1. Implement Health Check:

    • Set up a health check endpoint or a periodic status check that can verify whether the Celery server is operational.
  2. Display Alert on App Panel:

    • If the health check fails, display a prominent alert on the app panel (either a banner or a notification icon) to inform users/admins of the issue.
    • Include a retry or refresh option in the alert to re-check the server status.
    • Include a link to the documentation on how to start/restart celery

Additional Context:
Feel free to suggest improvements or additional checks for this process.


Acceptance Criteria:

  • Health check endpoint for Celery server status is implemented.
  • Alert displays on the app panel if the Celery server is down with link to documentation.
  • Alert is removed when Celery is back up.
@Yadavanurag13
Copy link

@kc-diabeat I would like to pick this issue.

@Daksh2000
Copy link

@kc-diabeat , If the issue is still available , can I pick ?

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

No branches or pull requests

3 participants