6.6 Policy Monitoring

Oracle TSAM Plus provides a comprehensive policy monitoring mechanism. When the proper policy monitoring settings are created, you can collect the exact metrics needed with minimum application performance impact. You define a policy using the TSAM Plus Web console and apply it to an Oracle Tuxedo application automatically. Oracle TSAM Plus Policy Monitoring has the following characteristics:

• Monitoring Category. One monitoring policy can focus on one kind of monitoring, such as call path. It can also cover multiple interested areas.
• Enable or Disable. Oracle TSAM Plus monitoring can be dynamically turned on or off. Monitoring policy can be predefined and enabled when the monitoring is required. All enabled monitoring policies will be applied to Tuxedo applications automatically while applications are running. Non-started applications will get the policy while it is started .
• Interval-Based Monitoring. Monitoring is initiated based on specific time intervals. For example, call path monitoring. An interval-based monitoring policy can specify that the call path is tracked in 60-second intervals.
• Ratio-Based Monitoring. Monitoring is initiated by the number of executions. For example, service monitoring. A ratio that is set to 5 indicates that every 5 executed services are monitored. For call path monitoring, a ratio set to 5 indicates that every 5 tpcall/tpacall calls are monitored.
• Runtime Condition Filtering. TSAM Plus monitoring policy supports some run time filters. Customer can monitor a particular service, a request from specific client and some kind of process type. The filter supports regular expression format.
• Flexibility to Reduce Monitoring Performance Impact. Oracle TSAM Plus monitoring control enables you to configure the monitoring policy based on your application size, load and network activity. The monitoring policy can support only alert triggering without raw metrics storage.