|
|
|
|
|
|
|
|
|
|
If be.engine.profile.*.file is specified and be.engine.profile.Agent_Class_Name.file is not specified, then the file name is the value of be.engine.profile.*.file, with the Agent_Class_Name appended.
If the properties be.engine.profile.*.file and be.engine.profile.Agent_Class_Name.files are not specified the name is created as follows: be-profile_Agent_Class_Name.csv
|
|
|
Default name is be-profile.csv and it is located under the current working directory, if file name is not specified.
|
|
|
|
|
|
When be.engine.profile.Agent_Class_Name.duration and be.engine.profile.*.duration are both present, the duration specified in be.engine.profile.Agent_Class_Name.duration takes precedence.
|
|
|
|
|
|
When be.engine.profile.Agent_Class_Name.level and be.engine.profile.*.level are both present, the level specified in be.engine.profile.Agent_Class_Name.level takes precedence.
|
To turn the profiler on In your rule or rule function, use the following function to turn on the profiler:
long duration: See
be.engine.profile.Agent_Class_Name.duration (Here
Agent_Class_Name is the current agent in which the rule or rule function that calls this function is executed.)
To turn the profiler off In your rule or rule function, use the following function to turn off the profiler:
Before you Begin Ensure that the property
hawk.enabled is set to true in the CDD at the cluster level before the TIBCO BusinessEvents engine starts.
To turn the profiler on Use the following method to turn on the profiler:
This method works the same way as the Engine.Profiler.startCollectingToFile() function (see
To Turn Profiler On and Off Using Functions), except that it requires you to specify an agent class.
String session: If you want to monitor multiple agents, execute the method once for each, specifying the agent class name in each case. If there is only one agent, the session parameter is optional.
To turn the profiler off In your rule or rule function, use the following function to turn off the profiler: