But these are also issues that the tests we??™ve previously
talked about don??™t handle very well. They are not issues that reveal themselves easily;
these issues can??™t be pinpointed with ???yes, I work??? statements, or even ???I don??™t work this way???
statements, as unit tests and exceptions can. No, these problems are going to require a little
more manual effort, and few more tricks that we??™ll talk about now.
Active Record and Logging
When it comes to scaling, probably the most important thing to keep an eye on is how much
activity is really going on. In other words, ???What??™s really happening when people use my application????
And logging key parts of your application is the simplest way to help answer that question.
The great thing about logging is that you have complete control over what information
you want to see. You can pick the critical spots in your code to log activity, and you can define
just what information you want to log at those points.
If you are using Active Record through Rails, logging will already be set up and quietly
running in the background for key events.
Pages:
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351