Trifle::Stats

Simple analytics backed by Redis, Postgres, MongoDB, Google Analytics, Segment, or whatever. It gets you from having bunch of events occuring within few minutes to being able to say what happened on 25th January 2021.

For comprehensive guides, API reference, and examples, visit trifle.io/trifle-stats-rb

Add this line to your application's Gemfile:

gem 'trifle-stats'

And then execute:

$ bundle install

Or install it yourself as:

$ gem install trifle-stats

require 'trifle/stats'

Trifle::Stats.configure do |config|
  config.driver = Trifle::Stats::Driver::Redis.new(Redis.new)
  config.track_ranges = [:minute, :hour, :day, :week, :month, :quarter, :year]
end

Trifle::Stats.track(key: 'event::logs', at: Time.now, values: { count: 1, duration: 2.11 })

Trifle::Stats.values(key: 'event::logs', from: 1.month.ago, to: Time.now, range: :day)
#=> {:at=>[Wed, 25 Jan 2023 00:00:00 +0000], :values=>[{"count"=>1, "duration"=>2.11}]}

Trifle::Stats supports multiple backends:

• Redis - Fast, in-memory storage
• Postgres - SQL database with JSONB support
• SQLite - SQL database in a file
• MongoDB - Document database
• Process - Thread-safe in-memory storage (development/testing)
• Dummy - No-op driver for disabled analytics

• Multiple time ranges - Track data across different time periods
• Custom aggregators - Sum, average, min, max with custom logic
• Series operations - Advanced data manipulation and calculations
• Performance optimized - Efficient storage and retrieval patterns
• Driver flexibility - Switch between storage backends easily

Tests are run against all supported drivers. To run the test suite:

$ bundle exec rspec

Ensure Redis, Postgres, and MongoDB are running locally. The test suite will handle database setup automatically.

Tests are meant to be simple and isolated. Every test should be independent and able to run in any order. Tests should be self-contained and set up their own configuration. This makes it easier to debug and maintain the test suite.

Use single layer testing to focus on testing a specific class or module in isolation. Use appropriate stubbing for driver methods when testing higher-level operations.

Driver tests use real database connections for accurate behavior validation. The Process driver is preferred for in-memory testing environments.

Repeat yourself in test setup for clarity rather than complex shared setups that can hide dependencies.

For performance testing:

$ cd specs/performance
$ bundle install
$ ruby run.rb 100 '{"a":1}'

Bug reports and pull requests are welcome on GitHub at https://github.com/trifle-io/trifle-stats.

The gem is available as open source under the terms of the MIT License.