Ahoy VS PaperTrail

A full-featured, mountable analytics dashboard for your Rails app, which is a blatant rip-off of heavily inspired by Plausible Analytics, powered by Ahoy. Open source, though lots of changing parts: https://github.com/joshmn/ahoy_captain

For logging which functions were used you can use ahoy

Ahoy may be worth a try https://github.com/ankane/ahoy

I've slowly started ripping Google Analytics out of my Rails projects and replacing it with https://github.com/ankane/ahoy.

It's so much better! I can just use SQL to see what's going in and not get overwhelmed with 100's of visualizations and complicated dashboards.

it's just a database table, so yeah, a migration is fine: https://github.com/ankane/ahoy/issues/461

I'm using the ahoy gem for analytics on my website (https://github.com/ankane/ahoy).

I did server-side tracking test in a rails app, where I implemented a tracking gem called ahoy and blazer for visualization. It is very easy to set up, but a bit hard to use. Blazer can do a very basic visualization of the data if you know your SQL queries.

https://github.com/ankane/ahoy The ahoy gem is pretty useful for this. Data model is pretty simple, it will track unique user sessions and metrics you specify will be associated with these sessions. The gem also parses the user agent, so it will indicate whether a session was on mobile, desktop or tablet.

if the source (web) application makes their own audit tables. ex: our ruby on rails application uses the paper-trail gem

Start with https://github.com/paper-trail-gem/paper_trail

We use paper_trail for this

I think you could use that in conjunction with the paper_trail gem, as /u/GreenCalligrapher571 mentioned, which is also a good suggestion. As an additional note, when changing records in production while using the paper_trail gem, I suggest wrapping your database-mutating statements executed in the rails console within a whodunnit block, so PaperTrail.request(whodunnit: 'Dorian Marié') { widget.update name: 'Wibble' } or something rather than just widget.update name: 'Wibble'. Or, if you have some sort of issue-tracking / ticketing system, you could set the whodunnit value to the ticket number or whatever, and then anyone who wants to know why the records are in the state they're in can consult that ticket, which hopefully has additional relevant context.

For a while we did this using the paper-trail gem. This was a very simple way to add a few lines of code to keep track of all of the changes made to an ActiveRecord model. But it came with one drawback. Every change to the data had to be done through ActiveRecord. There are often times when this makes an app vulnerable to a race condition. I’ll use a contrived example so as not to share any real code from our client’s app.

In most designs, this would probably not be possible unless a table tracking extension is being used in an ORM. Even with change tracking enabled through extensions like paper trail or Django simple history, it can be tricky to restore deleted entities. Object tracking would need to have been enabled before it is needed to ensure the data is still around to be restored.

Maybe you are looking for the papertrail gem? https://github.com/paper-trail-gem/paper_trail