A batch job consists of a large number of grouped operations on different data. The batch items may be split apart and processed one at a time, in serial or parallel. Observing a batch implies understanding both the individual processing of each item, and the batch-wide throughput. In a batch job, individual items are often processed by service calls; see our section on Service Calls for the pattern for processing single requests.
A batch job itself can be seen as one big Service Call request, as it usually starts with an invocation. Therefore, start with the section on Service Calls; this section only adds.
Questions that might want to be asked of a batch job might include:
The endpoint that starts the batch should be seen as the service entry.
The batch as a whole. (In addition, the items within the batch should be instrumented as services)
In addition to the aspects in the Service Calls section:
Instrument the processor for individual items that may be of interest to you and your team.