-
Notifications
You must be signed in to change notification settings - Fork 80
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
Prometheus exporter #109
Comments
@jkemp101 is the perfect person to talk about this. |
I think there are three different areas for tasktiger metrics. The first bullet is pretty easy. I've only been working slowly on the other two.
|
A contrib folder for a prometheus exporter daemon example sgtm. For task and worker metrics, would an example task decorator be sufficient? That's how I currently export task timing and success/failure metrics from all tasks. |
I think an example using a decorator would be good first step to show how to export those metrics. Are you just starting the prometheus http server in a separate thread from the main tasktiger process to export the metrics? |
Is it in progress? |
I think you can refer to the practice of the lib of php prometheus client. php-fpm worker is a short lived process too. I think it is a good way to flush stats to redis in stead of disk. @jkemp101 |
Now that #108 provides queue metrics, next we should build a Prometheus exporter to aggregate and monitor these metrics.
I guess that would be a daemon that could be installed on a single machine to export
Task.task_count_from_queue
and make them available for Prometheus.It's common for the Prometheus exporter to be tightly integrated into a product, for example:
https://www.cockroachlabs.com/docs/stable/monitor-cockroachdb-with-prometheus.html
The text was updated successfully, but these errors were encountered: