If you get that error, like me

add

#lib/resque-job-stats/server.rb
require 'resque/plugins/job_stats'

This data doesn't seem to be included in the UI:
Jobs enqueued as timeseries data (minute, hourly)
Jobs performed as timeseries data (minute, hourly)

Add to the Job_Stats UI view

Fantastic little gem, very useful. I had installed this via rubygems and got a version that, when extending my classes with JobStats, didn't provide all the stats as listed in the README. But grabbing directly from the master branch of the repo brought in those missing parts.

May be time to freshen the version up at rubygems.org?

The resque-job-stats.gemspec file uses a pessimistic version constraint to lock the bundler version as ~> 1.1.0. Due to the recently-announced CVE-2013-0334, it is best if all gemspecs update to 1.7.0 at a minimum.

This was caught by Gemnasium.

locking down the bundler version in the Gemfile isn't necessary since you must have bundler installed to use the gemfile. it forces devs to use the same (most likely older) version of bundler.

I've done this as a workaround in my BaseJob superclass:

# JobStats is implemented in such a way that we can't just extend a superclass:
# https://github.com/alanpeabody/resque-job-stats/blob/master/lib/resque/plugins/job_stats.rb#L19-L21
def self.inherited(subclass)
  subclass.extend Resque::Plugins::JobStats
end

Not expecting this to be fixed since the lib appears not to be maintained anymore, but perhaps this helps someone else.

i'd do a pull request but i've already screwed compatibility and this fix is pretty trivial
doh:
def jobs_duration_key
@jobs_failed_key ||= "stats:jobs:#{self.name}:duration"
end

Where should this be required in a Rails app?

I am no longer using Resque or this library. I am happy to hand of maintenance to anyone who is actively using this.

In modules Resque::Plugins::JobStats::Duration and Resque::Plugins::JobStats::History I see two different callbacks that start from around_perform_? From what I understand it means that job run twice to measure the time, is it intentional behaviour?

I'm trying to make this gem work with ActiveJob and this is how I can make around_perform_ callbacks work

         base.around_perform do |job, block|
            job.class.methods.select do |meth|
              meth.to_s.start_with?("around_perform_")
            end.each do |meth|
              job.class.send(meth) { block.call }
            end
          end

but in this case if we have more than 1 callback we call job few times. Could we discuss it?

Per http://yehudakatz.com/2010/12/16/clarifying-the-roles-of-the-gemspec-and-gemfile/ Gemfile.lock is not recommended to be checked in to version control.

This code seems like it is subject to race conditions, and could result in @measured_jobs being initialized more than once, and previous value clobbered.

  def self.measured_jobs
    @measured_jobs ||= []
  end

Hey there,

Will this be addressed soon?
I see the warning and iam using resque 1.25.2 currently.
Resque::Helpers will be gone with no replacement in Resque 2.0.0

Thanks
Jag

Hello,

We had a couple of issues recently where some time series values got an empty string without expiration.

Shouldn't the code in https://github.com/alanpeabody/resque-job-stats/blob/v0.4.2/lib/resque/plugins/job_stats/timeseries.rb#L50 be wrapped with a MULTI command ?

We can get a PR going if their is willingness to merge it.

Thanks!

How do we reset the history to 0?

Hey there!

I'm gearing up to work on Resque 2.0, and I'd like to coordinate better with plugin authors to make sure stuff doesn't break.

I'd like to know a few things:

1. Can I do something to help get you testing against edge Resque?
2. Are you monkey-patching anything in Resque currently? Can 2.0 expose an API to help you not have to do that any more?
3. Do you need any help in bringing your plugin up-to-date with the latest Resque?

Thanks!

Related: https://github.com/defunkt/resque/issues/880