Statistics

Statistics are automatically generated in the Sterling Order Management System Software.

The System Management Console gets most of its measurements from data found in the YFS_STATISTICS_DETAIL table.

Sterling Order Management System Software Statistics records, by default, are generated every 10 minutes for each active API and transaction running in each application server or Integration Adapter. For example, if the Schedule transaction was active in 3 Integration Adapters, you have 3 sets of statistics for each measurement interval.

Time-triggered transactions, at a minimum, generate the following four metrics:

  • The GetJobsProcessed metric indicates how many times Get Jobs were issued to look for work for this transaction.
  • The ExecuteMessageCreated metric indicates how many records were selected for processing.
  • The ExecuteMessageSuccess metric indicates how many messages were successfully processed.
  • The ExecuteMessageFailure metric conversely indicates how many messages were not successfully processed.

With these four metrics, you could:

  • Track ExecuteMessageSuccess to see how much work the application is processing throughout the day.
  • Track the ratio of ExecuteMessageSuccess divided by ExecuteMessageCreated to get an idea of the effectiveness. For example, a ratio of 0.8 means that only 80% of the orders are successfully processed. If the effectiveness ratio is consistently low, it could indicate that the application is encountering a large number of work (or orders) that repeatedly fail. This could lead to extra processing overhead.
  • Calculate the resource cost per unit work processed by correlating the number of works processed against the CPU consumed. You could track this to see if the cost per unit work is changing. This metric is useful for identifying areas to optimize. It is also the basis for computing resource capacity forecasting or planning.

In addition, some transactions produce transaction specific statistics. For example, some of the metrics the Schedule transaction generates includes NumOrdersBackordered, NumWorkOrdersCreated, and so forth.