# Locking issues in sidekiq jobs?

**URL:** <https://meta.discourse.org/t/locking-issues-in-sidekiq-jobs/69287>\
**Category:** Product Support\
**Created:** [3 Settembre 2017, 1:49pm UTC](https://meta.discourse.org/t/locking-issues-in-sidekiq-jobs/69287 "2017-09-03T13:49:34Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)\
**Post date:** [2 Gennaio 2019, 9:44pm UTC](https://meta.discourse.org/t/locking-issues-in-sidekiq-jobs/69287/6 "2019-01-02T21:44:48Z")

</div>

The plan is to add additional logging to track sidekiq job duration, and various metrics such as DB time and Redis time.

We’ll also regularly log “currently running jobs” on a regular basis, to help track things down in the event of a crash.

I think it should be ready in 2-3 weeks time.

---

_[View the full topic](https://meta.discourse.org/t/locking-issues-in-sidekiq-jobs/69287)._