It can be argued that the best and perhaps only real true measure of performance for any computer system is how long it takes to respond to a user's request for information or, en masse, how long it takes to respond to all users' requests. Given that this is the case, and we would argue that it is logically obvious, then the only sensible way to monitor the performance of any particular system is to measure the amount of time it takes to respond to those requests.
When it comes to database performance monitoring, with which we are concerned in this paper, most performance monitoring tools still don't measure how long it takes to do things, but instead focus on counting the number of things that have to be done. A time-based approach to measuring performance is not only more intuitive but is also more effective, not just in monitoring performance per se, but also in identifying the root cause of any problems that may arise.
Specifically, this paper discusses the various issues that surround database performance monitoring and how we believe that they should be addressed. Having identified the characteristics that you should be looking for in such a system we then go on to describe a solution, Ignite from Confio Software, which meets these characteristics.