[ Thanks to BlueVoodoo for this link.
]
“As you know from Part 1 of this three-article series,
it’s important to monitor the availability and performance of Java
applications and their dependencies in production to ensure problem
detection and accelerate diagnosis and triage. Source-code-level
instrumentation of classes you want to monitor can have the
advantages I discuss in Part 1, but it’s frequently not permissible
or practical. For example, many of your interesting monitoring
points might be in third-party components for which you don’t have
the source code. Here in Part 2, I focus on methods of
instrumenting Java classes and resources without modifying the
original source code.”