3 ms·

It would be a good idea to get some more robust logging into Rails 4.1. Rails has grown up, and so have many of the applications using it. Rails logging starts

It would be a good idea to get some more robust logging into Rails 4.1. Rails has grown up, and so have many of the applications using it. Rails logging starts to brake down when you need to track down the specific server and PID that is associated with an error. If you use a log aggregator, without information on PID and server, log messages interleave, and become hard to visually associate when you have 100 rails processes distributed across 10 servers.

purephase 13y ago
Which is where Scout, Honey Badger and New Relic come in. But, I agree, a more robust version for development environments would be nice.
- anko 13y ago
  stuff you need to pay for? There is surely a case for including some production logging in rails as default?
  - mmlac 13y ago
    I would argue that the standard rails logs are perfectly fine for local development and debugging. NewRelic even ships a local version that allows to track down performance issues. This works great for one or two requests triggered by the developer, but fails when thousands of requests bombard a live application split over a multiple servers with multiple rails instances running on each.
- mmlac 13y ago
  Scout, NewRelic and HoneyBadger are great tools to get started with. Their limitations are that they do what they do, how they think it should be done. If you need different metrics, another way to split up the data or correlate your mongo logs with app requests via NewRelic, you are out of luck. This is when creating your own logs with exactly the data you needs becomes valuable, when you can measure what you need how you need. My first post set the foundation for being able to easily get the right metrics and information by creating solid logs. It does not mean that this has to completely replace the aforementioned tools, on the contrary, it can supplement them to give you exactly the data you need when you need it.

purephase 13y ago

Which is where Scout, Honey Badger and New Relic come in. But, I agree, a more robust version for development environments would be nice.

anko 13y ago
stuff you need to pay for? There is surely a case for including some production logging in rails as default?
- mmlac 13y ago
  I would argue that the standard rails logs are perfectly fine for local development and debugging. NewRelic even ships a local version that allows to track down performance issues. This works great for one or two requests triggered by the developer, but fails when thousands of requests bombard a live application split over a multiple servers with multiple rails instances running on each.
mmlac 13y ago
Scout, NewRelic and HoneyBadger are great tools to get started with. Their limitations are that they do what they do, how they think it should be done. If you need different metrics, another way to split up the data or correlate your mongo logs with app requests via NewRelic, you are out of luck. This is when creating your own logs with exactly the data you needs becomes valuable, when you can measure what you need how you need. My first post set the foundation for being able to easily get the right metrics and information by creating solid logs. It does not mean that this has to completely replace the aforementioned tools, on the contrary, it can supplement them to give you exactly the data you need when you need it.