Parallel and serial sub-path elapsed time
In parallel sub-paths, if the minimum elapsed time for sub-path A is 200 milliseconds and the minimum elapsed time for sub-path B is 100 milliseconds, 100 milliseconds is published as the minimum elapsed time for the entire transaction pathway.
In serial sub-paths, if the minimum elapsed time for sub-path A is 200 milliseconds and the minimum elapsed time for sub-path B is 100 milliseconds, 300 milliseconds is published as the minimum elapsed time for the entire transaction pathway.
Section | Field name | Description | Rqd | |
---|---|---|---|---|
Totals | Name | Name of the Total. The name must be unique. No character limit. | x | |
Evaluate | Determines how the totals are ascertained. Options are: Serial – The path is treated as a single path such as A > B > C > D. The number of completed transactions is the minimum of that of the path evaluated. The average elapsed time is the sum of the averages. Parallel – paths where a message takes one route or another. Total of the independent sub paths taken: A > B The number of completed transactions is the sum of all sub-paths. The average elapsed time is the average of the sub-path averages. | x | ||
Model SLA metrics selection | ||||
Available | List of available transaction pathway SLA metrics to select and move to the selected list. Depending on your SLA needs, there are options on this tab, the Model Attributes tab, and Model SLA Metrics tab that might need to be configured. There is even an activity property (label) that you might need. | |||
Selected | List of selected transaction pathway SLA metrics chosen from the available list. | |||
History | Model SLA metrics history template | Allows history collection of the published SLA metrics allowing use of reports and trend charts. | ||
Transaction payload data metrics history template | Allows history collection of the published SLA metrics allowing use of reports and trend charts. |
Comments
Log in or register to comment.