The profiler utility collects statistics relating to the run to completion (RTC) rule evaluation cycle in an inference agent. The utility does not collect data about object management. It also does not collect data for other types of agents. It helps you understand, for example, internal execution times and frequencies of rules.
The profiler records time spent during each RTC on activities such as number of times each condition or action is performed, and total time spent on each condition and action. A complete RTC includes conditions and actions, although any individual RTC might contain only conditions or only actions.
Statistics are collected for each completed RTC. When the profiler is directed to stop during an RTC, it continues to collect data for the current RTC until that RTC is completed.
When the profiler is turned off, it continues to write statistics for the current session until that session is completed. So the RTC in progress is always completed, even if the profiler is directed to stop during an RTC.
Using properties Profiler turns on when the agent initializes at system startup. Used to profile RTC time, including startup rule functions.
Using TIBCO BusinessEvents catalog functions Profiler turns at the beginning of the next RTC after the function call, if it has not already been enabled. (There is no effect if the profiler is already on). Used to turn the profiler on and off inside a rule or rule function.)
Using a TIBCO Hawk method Profiler turns on by invoking a TIBCO BusinessEvents microagent Hawk method. Profiler is turned on at the beginning of the next RTC after the method call, if it has not already been enabled. (There is no effect if the profiler is already on). Used to dynamically turn the profiler on and off.
See Profiler Reference for a reference to all output data file column headings.