Skip to content

Add Configuration Option for Sidekiq Job Lifecycle Logging #310

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

Open
luis30n opened this issue Jan 28, 2025 · 0 comments
Open

Add Configuration Option for Sidekiq Job Lifecycle Logging #310

luis30n opened this issue Jan 28, 2025 · 0 comments

Comments

@luis30n
Copy link

luis30n commented Jan 28, 2025

Context

I have an application that runs millions of jobs daily and use NewRelic to aggregate logs. While analyzing the logs, I noticed that, starting from Semantic Logger v4.16, the gem logs every started and completed Sidekiq job by default, with no option to disable this behavior.

Given the high volume of jobs, these logs can become overwhelming and may lead to unnecessary noise in log aggregation tools like NewRelic.

Proposal

Would it be possible to introduce a configuration option to control the logging of Sidekiq job lifecycle events (started and completed)? This would allow us to enable or disable these logs based on their use case. To maintain backward compatibility, the option can default to enabled (current behavior).

I’d be happy to contribute by submitting a PR if we agree on this feature request.

Thank you for your time and for maintaining such a fantastic gem!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant