Monitoring

Monitoring can be thought of a the process of spying. We can all remember the greatest of all secret agents, not that half-wit 007, but the one and only Lancelot Link Secret Chimp, staking out Dr. Strangemind, Dragon Woman, Ali Assa Seen, or The Baron, head of C.H.U.M.P. Lance would embed sensors in the targets home, office, car, or close to some other critical region. Lance would then wait a listen for any information that these sensors might find. He'd listen to hear what these monitorables might offer up in the way of information that would give him a tip as to their performance. Monitoring in GAT is no different, except, of course, for the fact that the monitorer and the monitoree aren't chimps.

Monitoring in GAT is the process of allowing one process, the listener, through various sensors embedded in a second process, a mointorable, to obtain information about this second process. Usually these embedded sensors are placed around critical regions in the code, for example at the end or start of the main loop of a program. These sensors allow the listener to listen for any information that these monitorables might offer up. The information that these sensors offer up is usually related to the performance of the mointorable, for example the number of iterations per second. Let take a look at some of the monitoring particulars.

• Get Metrics
• Listening and not Listening for MetricEvents