concept tracing in category aspectj

This is an excerpt from Manning's book AspectJ in Action, Second Edition.
Compare this class with the one in listing 1.1: all the code to perform tracing—the ancillary concerns from the class’s point of view—have been removed. When you apply the same process to other crosscutting concerns, only the core business logic remains in the class. As you’ll see in the next section, an AOP implementation combines the classes and aspects to produce a woven executable.
Tracing is one of the most common monitoring techniques used to understand a system’s behavior. In its simplest form, tracing logs messages that describe the occurrence of interesting events during the execution of a system. For example, in a banking system, you would log each account transaction with information such as the nature of the transaction, the account number, and the transaction amount. You could also log exceptions that occurred during execution of the system along with the context under which they occurred.
During the development cycle, tracing plays a role similar to a debugger. It’s also usually the only reasonable choice for debugging distributed systems or concurrency-related problems. By examining the log, you can spot unexpected system behavior and correct it. A log also helps you see the interactions between different parts of a system to detect exactly where the problem might be. Likewise, in fully deployed systems, tracing acts as a diagnostic assistant for finding the root cause of the problem.
As you can see, the tracing calls are all over the core modules. When a new module is added to the system, all of its methods that need tracing must be instrumented. Such instrumentation is invasive, causing tangling of the core concerns with the tracing concern.