We use cookies or similar technologies to personalize your online experience and tailor marketing to you. Many of our product features require cookies to function properly. Your use of this site and online product constitutes your consent to these personalization technologies. Read our Privacy Policy to find out more.


Batch jobs

What can you observe?

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:

What is the top of the stack?

The endpoint that starts the batch should be seen as the service entry.

What is the unit of work?

The batch as a whole. (In addition, the items within the batch should be instrumented as services)

What context is useful to capture?

In addition to the aspects in the Service Calls section:

What comes next?

Instrument the processor for individual items that may be of interest to you and your team.