Open topic with navigation

TIBCO BusinessEvents® Enterprise Edition 6.3.1

# Profiler Reference

The table in this section explains each of the columns in the Profiler report. Data is grouped by `RTC_Stats_Type` and Description. (Description contains information about the specific RTC.) All data collected for conditions and actions performed during each RTC is listed within each RTC grouping.

Three rows of column headers for the RTC, condition, and action are listed at the beginning of the file:

- One for statistics relating to the overall RTC
- One for statistics relating to conditions
- One for statistics relating to actions.

The first column of each data line is always the statistic type, which begins with one of `RTC-`, `CONDITION-`, or `ACTION-`.

Data is also grouped, one row for the overall RTC, and zero or more rows for different conditions or actions or both, as appropriate.

Profiler Column Heading Reference (Sheet of )
Column Heading | Notes
--- | ---
Statistics Relating to the Overall RTC
`RTC_Stats_Type` | Type of rule evaluation cycle (RTC) There are 10 different types of RTC: `RTC-Object-Asserted` `RTC-Object-Modified` `RTC-Object-Deleted` `RTC-Event-Expired` `RTC-Execute-Rule` `RTC-Invoke-Action` `RTC-Invoke-Function` `RTC-Post-Process` `RTC-Repeat-TimeEvent` `RTC-Reevaluate-Element`
`Timestamp` | The time at which the first RTC begins.
`Description` | Information relating to the current `RTC_Stats_Type`. For example, the description of type `RTC-Object-Asserted` is the name of the object being asserted.
`NumExecuted` | The total number of times the same RTC has run.
`TotalRtcTime` | Total time in milliseconds spent on the total number of executions of the same RTC.
`AvgRtcTime` | `TotalRtcTime` / `NumExecuted`
`MaxRtcTime` | The maximum time in milliseconds spent on a single RTC.
`MinRtcTime` | The minimum time in milliseconds spent on a single RTC.
`MaxResolvedTime` | The maximum time in milliseconds spent to resolve a single RTC, include condition evaluation and action execution, but exclude operations related to object management (OM).
`MinResolvedTime` | The minimum time in milliseconds spent to resolve a single RTC, include condition evaluation and action execution, but exclude operations related to object management (OM).
Statistics Relating to Conditions
`CONDITION_Stats_Type` | Type of rule condition. One of the following: `CONDITION-Filter` `Condition-Join`
`Timestamp` | The timestamp of the first time the RTC begins.
`RuleDescription` | Name of the rule containing the condition, or name of the state machine transition rule containing the condition.
`ConditionDescription` | Condition statement of a rule or a state machine transition rule for user-defined condition, or predefined condition name for internal conditions. When a user-defined rule condition has a commented-out line, the `ConditionDescription` of the next condition is
    //… Only applies to CONDITION_Stats_Type
`NumEvaluated` | The total number of times this condition is evaluated in the same RTC.
`NumEvalTrue` | The total number of times the `Join` condition evaluated is true. This value is the sum of `NumEvalTruePropagatedLeft` and `NumEvalTruePropagatedRight`.
`TotalTime` | Total time in milliseconds spent on the total number of condition evaluations.
`AvgTime` | `TotalTime / (NumLeftSearch + NumRightSearch)`
`MaxTime` | The maximum time in milliseconds spent on a single condition evaluation.
`MinTime` | The minimum time in milliseconds spent on a single condition evaluation.
`NumEvalPropagatedLeft` | Number of times the join condition evaluation is triggered by object assertion propagated from the left side of the condition.
`NumEvalTruePropagatedLeft` | Number of times the join condition evaluates to true and evaluation is triggered by object assertion propagated from the left side of the condition.
`AvgRateEvalTruePropagatedLeft` | The average rate that the condition evaluates to true and evaluation is triggered by object assertion propagated from the left side of the condition.
`MaxNumEvalTruePropagatedLeft` | The maximum number of times the join condition evaluates to true and evaluation is triggered by object assertion propagated from the left side of the condition.
`MinNumEvalTruePropagatedLeft` | The minimum number of times the join condition evaluate to true and evaluation is triggered by object assertion propagated from the left side of the condition.
`NumEvalPropagatedRight` | Number of times the join condition evaluation is triggered by object assertion propagated from the right side of the condition.
`NumEvalTruePropagatedRight` | Number of times the join condition evaluates to true and evaluation is triggered by object assertion propagated from the right side of the condition.
`AvgRateEvalTruePropagatedRight` | The average rate that the condition evaluates to true and evaluation is triggered by object assertion propagated from the right side of the condition.
`MaxNumEvalTruePropagatedRight` | The maximum number of times the join condition evaluates to true and evaluation is triggered by object assertion propagated from the right side of the condition.
`MinNumEvalTruePropagatedRight` | The minimum number of times the join condition evaluate to true and evaluation is triggered by object assertion propagated from the right side of the condition.
Statistics Relating to Actions
`ACTION_Stats_Type` | Type of Actions. There are 10 RTC types and four action types. The four action types are: `ACTION-Rule-Action` `ACTION-Event-Expiry` `ACTION-Invoke-Action` `ACTION-Invoke-Function`
`Timestamp` | The timestamp of the first time the action execution begins.
`Description` | Information about the action corresponding to the current action type. For example, the description of type `ACTION-Rule-Action` is the name of the rule.
`NumExecuted` | The total number of times the same action has been run. A complete action has two phases, action execution and operation.
`TotalActionTime` | Total time in milliseconds spent on the total number of actions.
    TotalActionTime = TotalExecutionTime + TotalOperationTime
`AvgActionTime` | `TotalActionTime` / `NumExecuted`.
`MaxActionTime` | The maximum time in milliseconds spent on a single action.
`MinActionTime` | The minimum time in milliseconds spent on a single action.
`TotalExecutionTime` | Total time in milliseconds spent on the total number of action execution phases. Action execution time is the time the Rete network spends on running the action, for example, time spent in creating new objects, deleting existing objects, and so on.
`AvgExecutionTime` | `TotalExecutionTime` / `NumExecuted`.
`MaxExecutionTime` | The maximum time in milliseconds spent on a single action execution.
`MinExecutionTime` | The minimum time in milliseconds spent on a single action execution.
`TotalOperationTime` | Total time in milliseconds spent on the total number of action operation phases. Action operation time is the time TIBCO BusinessEvents spends on applying changes to the Rete network, for example, time spent asserting newly created objects, or retracting deleted objects.
`AvgOperationTime` | `TotalOperationTime` / `NumExecuted`.
`MaxOperationTime` | The maximum time in milliseconds spent on a single action operation.
`MinOperationTime` | The minimum time in milliseconds spent on a single action operation.
`MaxAgenda` | The maximum size of the rule agenda as a result of all action operations.
`MinAgenda` | The minimum size of the rule agenda as a result of all action operations.

Did you find this helpful?

YesNo
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO BusinessEvents® Enterprise Edition

Copyright © 2004-2024. Cloud Software Group, Inc. All Rights Reserved.