-
Notifications
You must be signed in to change notification settings - Fork 19
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
Add logging when job starts #4
Comments
Hi @stanhu,
|
@iMacTia Thanks, makes sense. For your reference, I evaluated this gem and another one to determine what we wanted for GitLab: https://gitlab.com/gitlab-org/gitlab-ce/issues/20060#note_66026811 I used your code as a basis for https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/18121/diffs, so thanks for starting this project. |
We've seen issues where Sidekiq jobs get stalled, and having the "start" message is incredibly helpful to know what was running before things got clogged. |
@stanhu I'm honoured you're considering one of my gems to be used in GitLab. This gem was born as a small helper to be used in some of my production systems by me and my team. I'm happy for you to use the code as you wish, but please consider to publish your improvements back into the gem so that everyone will benefit, if that's possible of course. I can also consider a merging/rebase of the gem into your organisation if that works better for you. |
Hi @iMacTia ! Thank you for this gem, we also are looking for this feature as well since we have started using this gem. I'm happy to send a pull-request to support this (maybe through a configuration flag). I would like to confirm that you are eager to have this in the repository, and if you are, I will send the pull-request. |
Hi @mdibaiee, of course! Improvements and contributions are always welcome! As far as you follow the guidelines I set out in my comment above I’d be more than happy to review and merge a PR 👍 Thanks for considering to contribute |
I noticed sidekiq-logstash doesn't log an event when a job starts:
sidekiq-logstash/lib/sidekiq/middleware/server/logstah_logging.rb
Line 12 in e3a5c70
That seems like valuable information. Is there any reason this isn't being done?
The text was updated successfully, but these errors were encountered: