Driven User Guide: Overview of Monitored Applications

version 2.2.6

1. Overview of Monitored Applications

1.1. Logging In

2. Searches, Saved Views, and Accessing Relevant Data

2.1. Starting a Search

3. Using the App Details Page

3.1. Searching App Details

4. Understanding the Unit of Work Details Page

4.1. Viewing Unit-of-Work Details

5. Managing Applications with Tags

5.1. Best Practice for Tags

6. Configuring Teams for Collaboration

6.1. Creating and Managing Teams

7. Using Annotations

7.1. Creating Custom Annotations

8. Execute Hive Queries as Cascading HiveFlow

8.1. Using HiveFlow

9. Execute Cascading MapReduce Flows
10. User Profile

10.1. User Actions

10.4. Invitations

10.5. Teams

Overview of Monitored Applications

Driven is the application performance management tool designed to help visualize and monitor data application performance on a cluster or in your local environment. This Driven User Guide describes how to utilize graphing, metrics, tabular, and collaboration features to diagnose runtime problems and improve application performance.

The Driven user interface is multilayered, ranging from a view summarizing the overall performance of multiple application, down to the granular level of individual slices during application execution. As you click on graphic visualizations and table cells, you can drill down from aggregated application metrics to a breakdown of the application execution details on the Hadoop cluster.

driven ui hierarchy
Figure 1. Layers of the Driven user interface

In addition to the graph examples here, data in each view is also displayed in tabular format.

Logging In

When you first log in to Driven, the page displays a status snapshot for applications that you have developed or will monitor. This is the My Apps page, which you can return to at any time by clicking on the navigation menu.

navigation menu
Figure 2. Navigation menu, with all view menu nodes collapsed

My Apps displays a compilation of status information for applications that are monitored by the Driven teams to which you belong. The My Apps page shows information from the data set that the All Apps page in previous versions of Driven used.

All Apps provides a status overview for applications that are monitored by your teams and applications that are the responsibility of teams to which you do not belong.

Typically, when you alternate between selecting All Apps and clicking My Apps on top of the navigation panel, the data on the page changes—​maybe just slightly—​but appears in the same format. Both All Apps and My Apps are similar to home pages of many applications and are a good place to start familiarizing yourself with Driven.

In All Apps, you may or may not have the ability to view more detailed information about application execution, such as application details or unit of work details, depending on which app visualizations that you click and on the system configuration. My Apps displays the accumulation of data only from applications that are associated with the Driven teams of which you are a member. As a result, you always can click the data that is displayed in a My Apps window to delve into underlying details.

All Apps and My Apps pages look and function the same as Status Views, except that they accumulate more data. These two pages are the highest-level visualizations of runtime performance for the applications that your Driven deployment is monitoring and can be helpful when you need to monitor or troubleshoot across the whole data cluster.

Status Views

In Driven, when you focus the application execution data by restricting the displayed information on the page by search terms or filter parameters and then save the criteria, you create a view. A Status View has more general information than the other type of view, which is a Periodic View. The Status View also lends itself to discovery of system-wide issues instead of specific application incidents.

Status view graphs with filtering and searching controls highlighted shows the search and filtering controls in the Status View. After you filter or search to focus on a subset of data, the status graphs display application information for the parameters that you set.

Apps View Driven2dot0
Figure 3. Status view graphs with filtering and searching controls highlighted

While Driven graphs provide a perspective of rolled-up data, tables underneath present a detailed breakdown of the graphical data. In tables you can view many additional dimensions of the selected application execution data. Depending on your immediate goals, the table is potentially more helpful than the graphs because information in tabular format is presented on a more granular level. See the Details Table section below for more information.

The Search feature supports several application-level query attributes. If you use the search field, you can filter the data that appears in all parts of the status view. Refer to Searches, Saved Views, and Accessing Relevant Data for detailed information.

Application and unit of work status throughout Driven, including the Status Change Events and Segment Frequency graphs, are represented by color-coded status categories of application and unit of work states:

Table 1. Application and Unit of Work Status Represented in Driven
State Color Icon



Pending State



Started State


Dark Blue

Running State



Successful State



Stopped State



Failed State

SUBMITTED (applies to units of work only)


Submitted State

SKIPPED (applies to units of work only)


Skipped State

Status Change Events

This graph represents a snapshot of application activity by displaying how many apps were in each execution status at various points of the time frame charted on the horizontal axis.

Hover over a node on a line graph to see the exact number of apps in the selected status at a specific point in time printed in the upper-left of the graph.
status change events

Segment Frequencies

By default, the Segment Frequency graph displays each application by name, how many times each app executed, and how often each app execution was in a particular status. This allows for comparison of application performance on a broad scale.

segment frequency graph
Hover over a bar in the graph to open a pop-up window that details the exact number of app executions for each segmented status.

Use the drop-down menu to change the metric of the vertical axis to measure performance along dimensions other than unique applications:

status frequency nameMenu Driven2dot0

Owner - Displays application data compiled by each application owner name.

Tags - Displays application data compiled by each tag term.

Team - Displays application data compiled by each team.

Tag Groups - If tags for any of the applications were grouped and prepended with a descriptor, click Tag Groups and select the group that you want to analyze. The resulting graph displays application data compiled by each tag term for the selected group.

If arrowheads to the right of the drop-down menu are enabled, then there are more data results than can fit in one page of the graph. Click the arrowheads to page through the graphed data set.

Auto-Refresh Data

Driven can refresh the displayed information as updates streamed in from the plugin. Ensure that the Auto Refresh toggle in the top right corner is enabled to allow the displayed Driven data to update in real time. If the Auto Refresh toggle is disabled, you must manually refresh the browser window to see data updates. Generally, this feature is useful if you want to monitor applications as they run.

Click the Auto Refresh control to toggle between off and on.

auto update slider
Figure 4. Auto Refresh slider

Details Table

The Details Table under the graphs provides a breakdown of application execution data by instance of each application run. Use the table to drill down and gain insights to application performance on your cluster. Some key monitoring assets of the tabular interface include the following capabilities:

  • Export application-level tabular data to a tab-separated values text file

  • Add or remove metrics that are displayed

  • Click on a hyperlinked application name to view app data on more granular levels, including visualization of units of work and steps as directed acyclic graphs (DAGs)

view table extract Driven2dot0
Figure 5. First few rows of a sample table

The Driven page displays a maximum of 25, 50, or 100 rows. Use the Page Size drop-down menu if you want to change the maximum number of rows.

If the number of rows spans more than one page after you have set the Page Size to your preference, use the pagination arrows to navigate to other pages of the table.

apps table pagination
You can reorder the columns by clicking column headings and dragging them to different locations. You can also sort the information in a column by ascending or descending order by clicking on the bidirectional arrow next to the column heading.
Track Applications by Various Metrics

Driven lets you customize most of the information that the table displays. Click the column chooser icon Counter Chooser 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. This helps with retrievability because the number of choosable columns can grow large.

A key feature of the table and column chooser is the ability to import and view counter attributes. See Counter Data and Other Metrics in Tables for more information.

Exporting Data to a .tsv File

As part of your analytical process, the application data that is presented in a Driven table can be downloaded as a tab-separated values (.tsv) file, which then can populate a spreadsheet for detecting patterns, metrics, and usage.

Click the download icon tsv icon to capture the Driven table data and download it to a file.