Writing stats to the log

[John Bachir]

I'd like to write sidekiq stats (https://github.com/mperham/sidekiq/wiki/Monitoring#monitoring-queue-backlog) to my application's log at a given interval, so that I can monitor it with librato (https://librato.com/). My first possibly misguided idea for doing this is to stick this in an initializer:

Thread.new do

  while true

    STDERR.puts "sidekiq queue size: Sidekiq::Queue.new.size"

    sleep 60

  end

end

Anyone have a better idea?

Thanks,

John

[John Bachir]

(and of course I meant STDERR.puts "sidekiq queue size: #{Sidekiq::Queue.new.size"})

[Mike Perham]

That's the basic idea and easiest thing to do.

--
You received this message because you are subscribed to the Google Groups "Sidekiq" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sidekiq+u...@googlegroups.com.
To post to this group, send email to sid...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sidekiq/562d96d3-51c3-4c78-8663-67c99c29fd63%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Mike Perham – CEO, Contributed Systems

Smart, effective open source infrastructure for your apps.

[Thibaut Barrère]

Hello,

here is a different idea (although not necessarily better!): we are using a rack endpoint which is monitored by pingdom (every minute).

The call is protected, outputs some text with the stats for us to quick-check, but can also push to statsd then to librato.

Hope this helps,

-- Thibaut

[John Bachir]

On Tuesday, June 16, 2015 at 4:04:16 AM UTC-4, Thibaut Barrère wrote:

here is a different idea (although not necessarily better!): we are using a rack endpoint which is monitored by pingdom (every minute).

The call is protected, outputs some text with the stats for us to quick-check, but can also push to statsd then to librato.

Yeah, that's what's proposed on the wiki: https://github.com/mperham/sidekiq/wiki/Monitoring#monitoring-queue-backlog

It's nice to have the option, but it doesn't fit in with how I do other monitoring so I don't really like it. I think a solution using logs/push is more appropriate than one using pull.

[John Bachir]

I remembered that that I already have a script which runs once per hour and reports various stats to another service. So I stuck this code at the bottom:

librato_queue = Librato::Metrics::Queue.new

%w[auth_mailer mailer default low].each do |queue|

  librato_queue.add "sidekiq.queue_size" => {value: Sidekiq::Queue.new(queue).size, source: queue}

end

librato_queue.submit