Please review and provide feedback

[heratyian]

@DPI-WE/technical-associates

[thierrychau]

Looks good!

• You don't need Rails.logger.info... if you use Papertrail right?
• I love Rollbar even in development. It gives a clean report for debugging.

[heratyian]

• You don't need Rails.logger.info... if you use Papertrail right?

there are 2 papertrails

One for storing and searching application logs https://papertrailapp.com/ Another is a gem for tracking changes to records https://github.com/paper-trail-gem/paper_trail

You still need Rails.logger.info, Rails.logger.error, or even a puts to log what's happening.

[thierrychau]

• You don't need Rails.logger.info... if you use Papertrail right?

there are 2 papertrails

One for storing and searching application logs https://papertrailapp.com/ Another is a gem for tracking changes to records https://github.com/paper-trail-gem/paper_trail

You still need Rails.logger.info, Rails.logger.error, or even a puts to log what's happening.

Ok, I think I get it. So this Rails.logger is for https://papertrailapp.com?

I thought the paper_trail gem, by tracking changes to records, was a way of logging, but now I understand that it's slightly different. Would be it good to mention this gem here, and state the differences?

Also, what are "good" events to log?

[heratyian]

Also, what are "good" events to log?

anything that helps you monitor your application. depends on what you want to track. https://stackify.com/rails-logger-and-rails-logging-best-practices/

[heratyian]

Adding paper trail gem here might be confusing. Maybe it should be it's own assignment "Tracking changes to your records" in Application Management, Analytics and Insights module. I'll add a todo here

[ahuynh3a]

I think this lesson is great! Straight to the point. No changes on my end :)