Sidekiq 6.0

[mperham]

Welcome to Sidekiq 6.0, the modernization release!

Changes:

• New log format: JSON! [JSON Logger Formatter #4050]
• Remove daemonization, pidfile and logfile options [RFC: Remove daemonization and logging control? #4045]
• Supported: Rails 5.0+, Ruby 2.5+, Redis 4.0+
• Larger pool size validation [Breaking changes #3970]
  Connection pool size must be >= (concurrency+2), which has been recommended for years now.
• REDIS_PROVIDER validation [Breaking changes #3970]
  Variable must not hold a URL.

[Tensho]

@mperham I have been thinking about the general approach for the multiple systems (Rails, Sidekiq, etc) logging in the context of the daemon hunt. The new world declares to spit the log entries primary to STDOUT/STDERR and abandons the log file. Does it mean Rails on Puma and Sidekiq (both are threaded systems) logs should be multiplexed in a one flow with the unified log entry structure and segregated with some sharp tools on demand? What kind of the centralized logging systems would you suggest? Sidekiq documentation always leads the best practices. For example, you provided a wonderful deployment documentation with systemd and upstart examples. It would be very helpful to have guidance about the logging either.

[mperham]

If you log to stdout and use systemd for your Ruby services, all log entries from puma, sidekiq, etc will all go into journald, where you can use systemd tooling to grep and inspect output from each service. You'd have to read the systemd docs for more detail, I'm not super familiar with all the options but I'm sure it integrates with syslog, for example.

I don't agree with their differentiation between STDOUT and STDERR but systemd does have a way to mark each logline with a level so systemd can ignore log output beyond a certain level (INFO, DEBUG, etc).

https://www.loggly.com/ultimate-guide/linux-logging-with-systemd/

[JanStevens]

Any chance on an update when version 6 will be released? We are holding back for it now (we really like the json logging)

[mperham]

When Rails 6 ships.

…

On Jun 20, 2019, at 00:51, Jan Stevens ***@***.***> wrote: Any chance on an update when version 6 will be released? We are holding back for it now (we really like the json logging) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[hjhart]

Hi @mperham – Rails 6 has shipped! Any update when this will be published?

[mperham]

When I’m not on vacation, poor timing on my part!

…

On Aug 19, 2019, at 17:53, James Hart ***@***.***> wrote: Hi @mperham – Rails 6 has shipped! Any update when this will be published? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[hjhart]

Seemed like there was no telling when rails was going to ship this release, so no, not poor timing. Enjoy your vacation! Look forward to hearing about a release at some point in the future.