Open sakari opened 3 weeks ago
We have some additional timestamps that may be useful for you such as: processOn: https://api.docs.bullmq.io/classes/v5.Job.html#processedOn finishedOn: https://api.docs.bullmq.io/classes/v5.Job.html#finishedOn It is a bit difficult to model a timestamp for every time a job is retried and moved to waiting status, not sure how we could improve this situation. The telemetry will include metrics but we must first support flows and groups, which is work in progress right now.
We would like to monitor the time jobs are in ready to be executed waiting for worker to detects congestion issues. As far as I can tell
timestamp
is the time the job was created which would not work that great if the jobs get put back to the queue from a worker -- eg with retry or delay. There is an issue from year or so ago about something similar. Is the answer still that we cannot get this information?As an aside, I saw that you are working on (opentelemetry) telemetry support which is great. On a quick look this seemed to focus on tracing only. Can we or or are there plans to expose bullmq metrics such as number of jobs etc through opentelemetry?