Are you still using plain text files to collect logs for your application? I was too until recently, but no more. While plain text logging is simple, it has a number of limitations. The good news is there are a number of superior logging alternatives available, including two that I have used personally—Loggly and Graylog. Read more on Up Your Logging Game with Improved Log Management Tools…
Screenshot / Merijn Vogel / CC BY 2.0
While certainly not the most elegant of debugging techniques, logging to a console is sometimes the most effective technique, and in many cases it’s your only lifeline. During development, sometimes a simple
“I am here” print statement can be a life saver.
Logging for Sinatra applications can be a bit tricky. When in development mode, exceptions are helpfully shown in the browser, or in your terminal where you started the application. In production, however, it takes some additional configuration to properly log requests and errors.
You’ve built your application. It does everything the customer asked for and everything he needs. Your designer’s polish has impressed everyone and your tool is a dream to use. Your comprehensive system test suite runs clean. Your exploratory tester can’t find any bugs you’ve missed. And you’ve got it deployed and running on its final home. So you must be done, right?
Wrong. It might be deployed and running – but now you have to keep it that way.