Driven User Guide: Using the App Details Page

The Status panel displays a color-coded bar representing the time the application spent in each of the states it was in. The states illustrated by the bar are labeled with begin and end times (time entered and time exited), or dates for long-running applications. For detailed information on these states, see Understanding the Driven State Model.

Below the timeline is the Progress section, which displays the total number of units of work the application has, along with tables that categorize the application’s units of work by state. The Active table’s columns are named for the active states that a unit of work could be in, while the Completed table’s columns are named for the end states that a unit of work could be in. The values in these columns are simple counters that show how many units of work are in the specified state.

If an application is still active, a Slice Rate graph appears below the Progress section, along with the current number of active slices and the time of last update. Mousing over the graph updates the time and number of active slices to those of the chosen point. For more information, see Counters.

The Metrics panel displays application-level aggregated counters. These metrics are collected by the Driven plugin or agent on each slice or step and rolled-up for an application-level view. For more information, see Counters.

The Properties panel displays a selection of information on the application. Some properties are collected by the Driven plugin or agent, while others are part of the plugin or agent’s configuration.

The following properties are shown:

The Environment panel displays different information depending on whether a Driven plugin or agent has been installed. Both versions of the panel display the following information about environment when available:

The Environment panel for an application with the Driven agent also displays agent information: version, JAR name, and JAR path.

The Environment panel for an application using Cascading includes the Cascading version in place of the Driven agent information.

Driven displays the status of each unit of work in an application in the rows of the Details Table. The status of an application instance is indicated by the icon at the top of the page under the application name.

The following is a list of the statuses:

- Pending status.

- Started status.

- Submitted status

- Running status

- Successful status

- Stopped status

- Skipped status

- Failed status

The Driven process object model consists of an Application as the root parent.

An Application can have any number of child Units of Work, which are analogous to Flows for those familiar with the Cascading model. Units of Work are composed of child Steps, which are composed of Nodes in turn. Slices are data concerning the actual instantiation and execution of logical nodes on the compute cluster. For example a logical mapper is a Node of the mapper type, which will then be instantiated multiple times and executed in parallel on the compute cluster in whatever slots can be allocated. Slice objects contain actual execution data such as counters and durations.

All Driven process objects, such as App, Unit of Work, and Step have a state, and progress through those states using a state machine explained below.

As soon as the Application client JVM starts, the Application is created in a "Pending" state. As the other logical application objects such as Units of Work, Steps and Nodes are created, they enter the "Pending" state.

Once processing is initiated, process objects move from "Pending" to "Started". When the client actually submits work to the compute cluster, the related process objects move into the "Submitted" state indicating that they are in the cluster queue. Applications can not be in a "Submitted" state as they represent the JVM that is submitting the work to the cluster.

Once an instance of a logical Node is actually executing on the compute cluster, the associated child and parents move into the "Running" state.

When all children have a completed state (Stopped, Successful, Failed, Skipped), The parent is also moved into a completed state.

The final Application state is based on the final state of the child Units of Work. Because there may be handled errors, Applications with failing Units of Work can be considered successful. The user can configure whether an Application with any failing Units of Work should be considered a failure using Driven plugin properties; see Driven Plugin

Because Slice data concerns actual execution data, Slices are really only ever in a running or completed state. For this reason no Slice data shows up in the Unit of Work detail view until they are running.

For applications in FAILED status, you can view the stack trace of these applications to further investigate for errors. Click the Show stack trace error button in the upper right corner to display the stack trace error information.

In addition, the failure status icon will show with a small info icon whenever there is a more detailed failure message for that object. You may see this icon next to a failed unit of work in the details table. This indicates that you can click on the icon to see the more detailed failure message and stack trace.

Driven helps you visualize instrumentation counters in a context to help you tune your applications. The Timelines of the Details Table provide detailed dashboards of unit of work that comprise the application, helping you to quickly identify which part of your application needs attention (assuming you will first attempt to tune the more resource-draining parts of the application).

Driven lets you customize most of the information that the table displays. Click the Select table columns icon to reveal or conceal columnar metrics. The Status and Name columns cannot be hidden.

The columnar metrics are categorized in the column chooser. Each category can be collapsed or expanded.

See Counter Data and Other Metrics in Tables for more information.