Driven 1.2 Release Notes

version 1.2

New Features

Navigation Pane with More Insights: Driven 1.2 has a navigation pane that enables quicker retrieval of views that surface more application execution metrics along a wider variety of scales. The navigation pane on the left side of each Driven window has branched-node families of the following views: Show All, Status View, Application View, My Teams, and Recent App Details.

Status Views: The Status View replaces the All Applications view of previous Driven releases. The view has interactive graphics, which can dynamically render detailed data in an informational context. The Status Timeline and Status Frequency graphs also accumulate and display more types of data in a dashboard format.

Application Views: A new view that graphs application execution instances on a timeline to help you monitor status, duration, and other telemetric data at a glance. The graphs also enable:

Interactive drill-down to metric details
Historical overlays for runtime data
Framing of data to standard and customized time intervals
Identification of when applications change status

Roll-up of Counter Data: The column chooser of the Status View, Application View, and application details view can import Cascading and Hadoop counter data to the Driven table so that you can automatically view aggregation of granular data. This feature can help you bypass deciphering multiple log files or calculating on the micro level to analyze your applications. Driven supports both standard and customized Cascading and Hadoop counters.

Saved Searches: If you have a set of search terms or filtering criteria that you want to save, you can save the search as a Status View or Application View. When you open the saved search, you see results that reflect up-to-date data.

More Search Parameters: The search parameters now include App Command and Tap Identifier.

Domain Tags: A domain tag consists of a tag term followed by a descriptor. The descriptor is helpful when the root tag term is applicable to more than one context. For example, the domain tags "cluster:test" and "cluster:prod" could differentiate two different types of clusters. The Status Frequency graph can be segmented by domain tag because it is a parameter recognized there. Domain tags are also selectable as column chooser attributes.

JIRA Integration: A team leader can integrate a running instance of JIRA with Driven. The link to the JIRA instance appears on views containing application and flow details. This enables team members to file an issue with contextual information about the application or flow more quickly.

Webhooks: Driven can be integrated with third-party messaging platforms to automatically notify people when an application reaches Successful status, Failed status, or a Completed state. Driven 1.2 supports webhooks that communicate with Slack, HipChat, and PagerDuty.

Unresponsive Applications: You can stop one or multiple unresponsive applications at the same time.

Enhancements

Graphs and counts display the Stopped application status when applicable.
Timeline data in a table can be exported to a .tsv (tab-separated values) file.
The Skipped status for a flow is displayed when applicable.
The My Teams links display the number of applications associated with each team.
You can filter the Status Frequency graph by team.
You can drag-and-drop the columns of a table in a Status View, Application View, or flow details view to rearrange the order. You can also reorder the items in a column by using the sorting arrow in the column header.

Fixed Bugs

Driven dropped data associated with very long flow or tap names. Excessively long names are now truncated.
Password reset interface was misleading.
Long tag strings distorted the display of the metadata information that appeared at the top of an app-level page.
Using the HDP-2.2 Sandbox and the Driven Plugin together displayed incompatible plugin due to application classpath exceeding character limits.
The Start:Run Duration column displayed a date instead of a time difference.
Starting Driven from the bin directory (via stand-alone Tomcat package) caused two issues:
- The ./conf relative path for the driven.properties file was not found.
- The default setting placed the Driven directory relative to the startup location, thereby putting the data dictionary in the bin directory.