active_record_doctor VS Blazer

Thank you for your contribution! How would you compare this gem to https://github.com/gregnavis/active_record_doctor?

Start with finding mixing indexes: https://github.com/gregnavis/active_record_doctor

What did you build the website with? It looks really nice and I’m looking for something I could use with my project. [1]

[1] https://github.com/gregnavis/active_record_doctor

gregnavis / active_record_doctor

I try to avoid these tools wherever possible, given the choice I'd always go for tools like Blazer.

https://github.com/ankane/blazer

No such luck in my current role, Looker and PowerBI are both in use by different bits of the org and nobody has the ability to delve into the underlying figures.

As u/jaxn said you could use Blazer for this kind of thing. I would also look into materialized views or custom tables and a scheduled job that calculates the metrics they care about. That will take you a long way. Eventually you can use something like Metabase but I would put that off for as long as possible as it's really expensive and pretty involved.

And it's Open Source: https://github.com/evidence-dev/evidence

I'd also highly recommend Blazer https://github.com/ankane/blazer if you are into the Ruby on Rails world. It's super solid, and it's been an indispensable tool integrated to all my projects.

I use Ahoy too, but I don't have very good visibility into the data. I should spend more time building queries and creating charts. I should probably set up blazer as well: https://github.com/ankane/blazer

blazer

The Blazer gem provides a nice way to analyze the results easily. It is simple to install and allows SQL queries to run against tables. The query here shows that the candidate implementation is significantly faster than the original.