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
Provide health check for celery beat #1102
Comments
@nniehoff - Is there any update to this? I've spotted that the health check applied to celery-beat in the Helm charts is |
Possibly something like this can help? celery/celery#4079 (comment) We are trialing this for the normal workers in a K8S environment |
That looks to be worker-specific to me, and what we're looking for in this issue is a healthcheck for beat rather than the workers. Thanks though! |
I thought that maybe there would be beat signals to cover the functionality, but it appears there is only beat-init and nothing after that. |
Desirable in LTM as well. |
Backported in #5430. |
Environment
We need to provide a healthcheck for Celery Beat. In the docker-compose development file, we are using
nautobot-server health_check
for the Celery pods today. Unfortunately, this health check doesn't check the health of the Celery worker or Celery beat. The helm chart uses a slightly different approach for the celery worker which is:This works great for the Celery workers, but it doesn't work for Celery beat. In some quick research, we may need to implement a simple function to make this happen. I wanted to get this open before we ship 1.2.
The text was updated successfully, but these errors were encountered: