Driven User Guide

Searches that you can initiate at top of the Driven window support several application-, process-, and tap-level query attributes. This is the starting point for mining Driven data if you do not have access to any saved views that can help you.

There are multiple parameters that you can invoke to query the application runs:

Figure 2: Search filter parameters

Figure 3: Status filter parameters

Figure 4: Column chooser icon and excerpt of selectable attributes

After searching for applications based on the criteria and filters you have defined, you can save the query as a view. You can then return to the view to retrieve all applications that match the search criteria and filters. Search results of a saved view are dynamic, displaying applications with matching search parameters at the time that the view is opened.

When you save the view, select what information about the matched applications to display:

Links to your saved views appear in the sidebar.

Figure 5: Saving a view

Your saved views can be retrieved by clicking them in the side panel.

Each item in the My Teams area of the side panel is an entry point to a status view that is associated with a team of which you are a member. All members of the same team have the same status view under My Teams. A My Team link opens to a status view that the same as the Show All view, except that the data is filtered to show only information that is correlated with the selected team.

When you are in a view that is displaying application-level data, Driven can refresh the displayed information as updates stream in from the plugin. Ensure that the Refresh toggle in the top right corner is enabled to allow the displayed Driven data to auto-refresh in real time. If the Refresh toggle is disabled, you must manually refresh the browser window to see real-time updates. Generally, this feature is useful if you want to monitor applications as they run.

Click and slide the Refresh icon to toggle between enabled and disabled.

Figure 6: Refresh icon

You can create custom searches for application runs that have specific attributes, such as having a certain time range for processing or populating a counter with a defined value range. Custom searches are based on Lucene query syntax, which is entered in the search field of a Search View or Application View.

As with searches that do not use Lucene query syntax, custom searches return applications that match your search-parameter values and that are associated with your Driven teams.

Table 1 shows some examples of the types of information that can be retrieved with a custom search and the query statements to obtain the application search results. Refer to the statement syntax examples in Table 1 for guidance on how to construct some types of Lucene queries. For detailed information about the required syntax in search queries, see Apache Lucene - Query Parser Syntax documentation.

Table 2 lists Cascading application attributes that are most relevant to searches in Driven. The most commonly used search targets, such as app name, are integrated in the Driven GUI so that you do not need to run a Lucene query to find matches. When an attribute can be located by a search filter or column chooser, Table 2 lists the part of the user interface that can be used to track the information.

Although an application attribute might be searchable with the GUI controls, you might prefer to query for the attribute and value in a Lucene query. This is particularly true when you want to find matches based on a range of values or if you want to run a complex query.

Elasticsearch truncates field values that exceed 16,000 characters. If a search parameter value includes characters that appear only in a string beyond the character limit (such as a very long classpath), Driven does not return a match because it is unable to search for possible matches after 16,000 characters of a string.