# Extending the current library with extra metrics
**URL:** https://meta.discourse.org/t/extending-the-current-library-with-extra-metrics/265019
**Category:** Feature
**Tags:** prometheus
**Created:** [February 2, 2021, 12:56pm UTC](https://meta.discourse.org/t/extending-the-current-library-with-extra-metrics/265019 "2021-02-02T12:56:47Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@uded](https://meta.discourse.org/u/uded)
#### Post date: [February 2, 2021, 12:56pm UTC](https://meta.discourse.org/t/extending-the-current-library-with-extra-metrics/265019/1 "2021-02-02T12:56:47Z")
Wouldn’t it be beneficial to include [GitHub - Strech/sidekiq-prometheus-exporter: All the basic metrics of Sidekiq with pluggable contribs prepared for Prometheus · GitHub](https://github.com/Strech/sidekiq-prometheus-exporter) in the project? For example, I am missing finished and failed job count with this plugin, and that is one of the most important metrics to see if something is failing…
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [February 2, 2021, 10:59pm UTC](https://meta.discourse.org/t/extending-the-current-library-with-extra-metrics/265019/2 "2021-02-02T22:59:53Z")
That project is entirely stand alone and not something we would integrate
If you are missing metrics make #Contribute > Feature request to add the or add in a PR
---
### Author:  [@uded](https://meta.discourse.org/u/uded)
#### Post date: [February 3, 2021, 9:01pm UTC](https://meta.discourse.org/t/extending-the-current-library-with-extra-metrics/265019/3 "2021-02-03T21:01:07Z")
Unfortunately Ruby is not my cup of tea, so making a PR seems like a bumpy road for me. I can give it a try, but there will be a steep learning curve for me. On the other hand, the official repo mentioned above doesn’t allow tickets to be created, hence I have a limited number of places where I can ask for new features. Namely – here.
Hence I am asking to extend the current library with the metrics listed below. Which is, not accidentally, the list of metrics from the library listed above. I already marked those that are available in the current version. The ones in bold seem to be the most obvious to fully monitor Sidekiq executing in the background.
| Metric | Type | Description | Already Implemented metric |
| --- | --- | --- | --- |
| ~~sidekiq\_processed\_jobs\_total~~ | counter | The total number of processed jobs | discourse\_sidekiq\_job\_count |
| **sidekiq\_failed\_jobs\_total** | counter | The total number of failed jobs | |
| ~~sidekiq\_workers~~ | gauge | The number of workers across all the processes | discourse\_sidekiq\_workers |
| ~~sidekiq\_processes~~ | gauge | The number of processes | discourse\_sidekiq\_processes |
| sidekiq\_busy\_workers | gauge | The number of workers performing the job | |
| ~~sidekiq\_enqueued\_jobs~~ | gauge | The number of enqueued jobs | discourse\_sidekiq\_jobs\_enqueued |
| sidekiq\_scheduled\_jobs | gauge | The number of jobs scheduled for a future execution | |
| **sidekiq\_retry\_jobs** | gauge | The number of jobs scheduled for the next try | |
| **sidekiq\_dead\_jobs** | gauge | The number of jobs being dead | |
| sidekiq\_queue\_latency\_seconds | gauge | The number of seconds between oldest job being pushed to the queue and current time (labels: name) | |
| sidekiq\_queue\_max\_processing\_time\_seconds | gauge | The number of seconds between oldest job of the queue being executed and current time (labels: name) | |
| sidekiq\_queue\_enqueued\_jobs | gauge | The number of enqueued jobs in the queue (labels: name) | |
Please, do correct me if I missed one or misunderstood something.