Common - Batch
The Batch subject areas leverage the batch run, submission, and execution objects.
Common - Batch Performance
This subject area exposes common metrics based upon batch control. These can be used as reference metrics in conjunction with other subject areas in this family.
Answer questions like these:
- What is the average execution time for a particular batch control?
- What is the confidence interval for execution times?
- How many executions are used in this metric?
Common - Batch Run History
Every time a batch process is executed, a number of objects are created and updated to track the progress of the process during and after execution. This subject area is provided to allow for strategic analysis using history of execution at the batch run level.
Answer questions like these:
- What is the trend for executing a particular batch control?
- What method is used to initiate batches and when?
- Are there particular users overly contributing to my batch workload by manual submission?
- Is volume a factor in run-time overruns?
- What types of batch processes are executing over time?
- What is the trend of the executions over the last few months?
- Is my execution failing regularly or are there sporadic failures?
- Is my batch workload using the service functionality or predominately extensions?
Common - Batch Run Thread History
Every time a batch process is executed, a number of objects are created and updated to track the progress of the process during and after execution. Each thread of execution is recorded for post-execution analysis.
Answer questions like these:
- Are the threads of a batch process ending at the same time or is there data skew in processing? If some threads are ending later, what could be the cause?
- Are there any threads that are outliers in terms of elapsed time?
- Are certain threads consistently using up the resources over other threads?
- Is thread processing consistent over time?
Common - Batch Thread Capacity History
Every time a batch process is executed, a number of objects are created and updated to track the progress of the process during and after execution. This subject area allows you to subdivide a date into desired time intervals (for example, 10- or 15-minute intervals), and tells you what was running during that period for capacity analysis.
Answer questions like these:
- Are there peaks in my daily thread processing that I can move to other times?
- Am I running too many batches at the same time?
- Can I distribute workload evenly over the period to reduce capacity requirements over time?
- What type of workload is being executed at any time in my physical day?