-
Notifications
You must be signed in to change notification settings - Fork 95
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
receiving celery_worker_tasks_active = 0 #172
Comments
Have you enabled worker_send_task_events in your app? https://docs.celeryq.dev/en/stable/userguide/configuration.html#worker-send-task-events |
@danihodovic Hey! thank you for the quick reply. yes, I have included in the application what you say. but I still don't get what I want. i use fastapi with celery
|
@danihodovic maybe the problem is that I'm using workers with gpu?
|
I don't think that should be a problem. Increase the log level of the celery-worker and see if it's logging anything interesting. |
@danihodovic how to enlarge the magazine? |
https://github.com/danihodovic/celery-exporter/blob/master/src/cli.py#L56 Either export an environment variable
or use a command line argument
|
@danihodovic I turned on the debug mode and made sure that all metrics are sent, except for task activity |
@danihodovic I also noticed that from time to time celery-exporter gives out non-existent hostnames. here is an example:
even though I gave my worker a name:
|
Are you sure you're running a single worker? The exporter reads the hostname from the celery events. |
@danihodovic yes, I am absolutely sure of it. above is the command i use in my docker-compose.yml |
@danihodovic the only moment I see now is the launch of flower. can there be problems because of this?
|
I'm not running flower so it's hard to tell |
Hello there! |
celery_worker_tasks_active{hostname="worker2"} 0.0
celery_worker_tasks_active{hostname="worker1"} 0.0
Hey! i get 0 active tasks even though there are currently 10. it seems to me that celery-exporter monitoring is not updating active tasks often enough
The text was updated successfully, but these errors were encountered: