-
Notifications
You must be signed in to change notification settings - Fork 0
Tracking
SharpBatch has a tracking system to track batch activity.
SharpBatch can use 2 Tracking systems
If anyone is configured SharpBatch will use default config as Tracking Memory.
SharpBatch implements this tracking informations
| Field Name | Description |
|---|---|
| BatchName | the name of executed batch |
| SessionId | The id used to identify the single batch execution |
| StartDate | Batch start date |
| EndDate | Batch end date |
| MachineName | The machine names that executes batch |
| Pings | Date Time of a received Ping |
| State | Batch status |
| Messages | Custom messages logged from Batch |
| Exceptions | Exception thrown by Batch execution |
Identifies the name of a tracked batch. This is the name of the class marked as a Batch.
Each Batch execution is identified by a GUID. SessionId is an Id to use for all Batch command.
This is the start and the end of batch execution. If the EndDate is null the batch could be on Running state.
The name of the machine that executes this session of a batch.
The list of the Pings received.
The status of a Batch execution.
The list of a messages that Batch can trace. Tracking a message is a feature that SharpBatch uses to track messages into tracking system. Batch class could write any information into Session Tracking area. At the end of execution you can read it on a Tracking.Web site.
The exception logged when Batch throws an exception.