Lograge VS Scenic

You can choose from a number of third-party logging libraries, including Logging — based on Java's log4j library — and Lograge. Lograge is a feature-rich logging library meant to simplify the often messy and verbose Rails logs characteristic of the default application logger.

Also a big fan of Lograge, because I just can't stand Rails default logs.

add lograge

To output rails logs into JSON format, we are using lograge gem once you add it in Gemfile and bundle install it will be available to use in you application.

There are plenty of options when it comes to picking up a 3rd-party logging framework. The most popular of these is Lograge. Let's take a look at it!

Check out https://github.com/roidrage/lograge for some settings that work nicely for us in production

To model our Deliverable class, we will need a view. We will use the popular scenic gem, which provides some useful generators for creating views with their respective migrations, and utilities to handle views versioning.

+1 for scenic - https://github.com/scenic-views/scenic

If the data doesn't need to be close to real-time, and if your DB can handle a bit of load, I'd use a "batch" approach. To do this, I'd create a materialized view in your relational DB that you'd then refresh periodically. The easiest way to do this is with the `scenic` gem. Once you've done this, you can simply create a new model and set the `table_name` to the name of the materialized view, and then treat it as a regular model.

I use the scenic gem to manage views which uses raw sql files: https://github.com/scenic-views/scenic

add scenic

TIL about fx gem for storing triggers in schema.rb. That makes me so happy because scenic gem for creating database views is one of my favorites. Postgres is very powerful and it's great to see tools for exposing that through Rails.