-
Notifications
You must be signed in to change notification settings - Fork 229
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
[FEATURE] Prometheus metrics #97
Comments
The INFO command provides basic metrics already but you'd have to pull them. I'm still in the process of deciding how to support various metrics standards like Prometheus and Statsd. |
Today I hacked together a very basic exporter. It isn't very powerful, just supports a few key metrics. |
Faktory Pro now has Statsd support. I will add first-class Prometheus support based on customer demand. |
@mperham Was there any work towards supporting exports to Prometheus? We would like to utilise those for alerting for our enterprise account. |
Not yet, you're the first to request Prometheus support. |
Adding my vote to support prometheus metrics! |
Thanks @lukasmalkmus for bringing this up and providing a first exporter. As I had problem to use your package from source as well as in a docker container, I've written a similar Python implementation: https://github.com/prospect-server/faktory-prometheus-exporter |
I'm keeping this short: I'm pretty sure the project and its users can benefit from exporting prometheus metrics. Metrics are important in modern application deployments, especially if there are many moving parts.
I would suggest to export some basic metrics about the application itself, queues, jobs and the web server (latency, http status codes, etc.). They are also interesting for scaling Kubernetes deplyoments: See #19.
If this is desired, we can discuss it in detail and I would love to contribute a basic implementation.
The text was updated successfully, but these errors were encountered: