Minuteman

Wikipedia: Minutemen were members of teams from Massachusetts that were well-prepared militia companies of select men from the American colonial partisan militia during the American Revolutionary War. They provided a highly mobile, rapidly deployed force that allowed the colonies to respond immediately to war threats, hence the name.

Origin

Freenode - #cuba.rb - 2012/10/30 15:20 UYT

conanbatt: anyone here knows some good web app metrics tool ?

conanbatt: i use google analytics for the page itself, and its good, but for the webapp its really not useful

tizoc: conanbatt: http://amix.dk/blog/post/19714 you can port this (if an equivalent doesn't exist already)

conanbatt: the metrics link is excellent but its python and released 5 days ago lol

elcuervo: tizoc: the idea it's awesome

elcuervo: interesting...

Inspiration

Installation

Important!

Depends on Redis 2.6 for the bitop operation. You can install it using:

brew install redis

or upgrading your current version:

brew upgrade redis

And then install the gem

gem install minuteman

Usage

Currently Minutemen supports two options :silent (default: false) and :redis (default: {})

Options

silent: when true the operations will not raise errors to prevent failures

time_spans: an Array of Minuteman compatible TimeSpan. Eg. %w[year month day] will only track events on that timespans. Ignoring the rest

redis: can be a Hash with the options to be sent to Redis.new or a Redis connection already established (Redis::Namespace works as well).

require "minuteman"

# Accepts an options[:redis] hash that will be sent as is to Redis.new
analytics = Minuteman.new

# You can also reuse your Redis or Redis::Namespace connection
analytics = Minuteman.new(redis: Redis::Namespace.new(:mm, redis: Redis.new))

# Mark an event for a given id
analytics.track("login:successful", user.id)
analytics.track("login:successful", other_user.id)

# Mark in bulk
analytics.track("programming:love:ruby", User.where(favorite: "ruby").pluck(:id))

# Fetch events for a given time (default is Time.now.utc)
today_events = analytics.day("login:successful", Time.now.utc)

# This also exists
analytics.year("login:successful")
analytics.month("login:successful")
analytics.week("login:successful")
analytics.day("login:successful")
analytics.hour("login:successful")
analytics.minute("login:successful")

# Lists all the tracked events
analytics.events
#=> ["login:successful", "programming:login:ruby"]

# Check event length on a given time
today_events.length
#=> 2

# Check for existance
today_events.include?(user.id)
#=> true
today_events.include?(admin.id)
#=> false

# Bulk check
today_events.include?(*User.all.pluck(:id))
#=> [true, true, false, false]

Bitwise operations

You can intersect sets using bitwise AND(&), OR(|), NOT(~, -) and XOR(^). Also you can use plus(+) and minus(-) operations.

set1 + set2
set1 - set2
set1 & set2
set1 | set2
set1 ^ set2

~set1 \
       |==> This are the same
-set1 /

Intersecting with arrays

Let's assume this scenario:

You have a list of users and want to know which of them have been going throught some of the tracks you made.

paid = analytics.month("buy:complete")
payed_from_miami = paid & User.find_all_by_state("MIA").map(&:id)
payed_from_miami.size
#=> 43
payed_users_from_miami = payed_from_miami.map { |id| User.find(id) }

Currently the supported commands to interact with arrays are & and -

Example

invited = analytics.month("email:invitation")
successful_buys = analytics.month("buy:complete")

successful_buys_after_invitation = invited & successful_buys
successful_buys_after_invitation.include?(user.id)

# Clean up all the operations cache
analytics.reset_operations_cache

Also you can write more complex set operations

invited = analytics.month("email:invitation")
from_adsense = analytics.month("adsense:promo")
successful_buys = analytics.month("buy:complete")

conversion_rate = (invited | from_adsense) & successful_buys

skarlcf / minuteman