Batchs monitoring

AppStatus provides a batch monitoring API, which can replace log calls and provides a better feedback on overall batch activity.

Add dependency

Batch monitoring is modular feature of App Status. This allows to implement custom persistence for these data.

App Status provides a default implementation, appstatus-batch-inprocess, which stores data in the current JVM. This means the overhead is very small but data are not shared between JVMs if your application runs on multiple servers and are lost when the application stops. 

<dependency>
            <groupId>net.sf.appstatus</groupId>
            <artifactId>appstatus-batch-inprocess</artifactId>
            <version>0.0.9</version>
            <scope>compile</scope>
</dependency>

Usage

		
IBatchProgressMonitor monitor = AppStatusStatic.getInstance().getBatchProgressMonitor( "Batch name", "Batch group", "Unique Id");

monitor.beginTask(  "Task name", "Task description" , 2 /* steps */ );

monitor.setCurrentItem( "1" ) ;

// Do some work on item 1;
...

// Set step completed.
monitor.worked(1);

monitor.setCurrentItem( "2" ) ;

// Do some work on item 2;
...

// Set step completed.
monitor.worked(1);

// End batch.
monitor.done();

The batch UUID is used to get the IBatchProgressMonitor object back when you have no way to keep it accessible within the different parts of your code. One example is when using Spring Batch. The same UUID always returns the same monitor.

Note: API is very close to the Eclipse Job API.

Result

Go to http://<server>/<app-context>/status?p=batch :

Batchs page example