Rails production log not updating
The five lines in the above example for a single 404 error are fairly typical of what you’ll see for all requests in a production log.
However, everything seems to be being written to /var/log/apache2/
I’ve seen some very effective use of application logging to debug difficult problems.
From a best-practices standpoint, I feel it is a bit severe to classify these errors as fatal since most logging conventions consider fatal errors as catastrophic and generally unrecoverable.
For these routing errors your server will continue happily working, send out a 404 response and go on to process future requests.
The foundation of good logging is being sure that your application is logging the right things.
However, it’s just as important for your log files to be easy to parse - both for a human reading the file and for any scripts that might be written to extract information from them.
In this article I’m assuming a relatively simple Rails application at the beginning of its lifecycle that runs as a single instance.
The application might have a handful of standard RESTful resources with their initial generated routing.
Our next goal is to turn the information logged for a single request into something that is parsable by both humans and computers.Tags: Adult Dating, affair dating, sex dating