TSAM SLA Monitoring
By Todd Little-Oracle on Oct 06, 2010
One of the most powerful features of TSAM is the ability to monitor Service Level Agreements. TSAM provides two alerting mechanisms. One allows you define alerts that should be checked by the TSAM console. As data is reported to TSAM Manager (the data collection and storage portion of TSAM) it is compared against alerts that have been defined in the console. This can be a great tool in monitoring your Tuxedo applications.
The one drawback though is that the data has to be reported to TSAM Manager. Given that many Tuxedo applications process 100's or 1000's of requests per second, if the monitoring policies for these kinds of applications enable reporting most of the information that can be collected, it is likely that the TSAM Manager component will be overwhelmed with too much data.
In order to provide finer grained monitoring and ensure that SLAs are being adhered to, TSAM allows alerts to be defined at the plug-in level. The triggering of these alerts is based upon an FML32 boolean expression against the monitoring data evaluating to true. Once an alert is triggered, an alert may be sent to the TSAM Manager, trigger a Tuxedo event to be processed by the Tuxedo EventBroker, and optionally have the message be dropped from the servers IPC queue in the event that there is no point in processing the request.
In my next post, I'll give the details on how these sorts of alerts are defined and some additional ideas about what sort of actions you might want to take place when these alerts are triggered.
Oracle Tuxedo Chief Architect