Driven User Guide
version 1.1.1Managing applications with the All Applications view
The All Applications view provides a broad view of all the Cascading applications executing in your cluster. Depending on how you organized your applications into the Teams feature (see Configuring Teams for collaboration and cluster management), including how you annotate your flows and taps, you can get meaningful insights into the behavior of your application.
By default, you will see all the Cascading applications that have been executed by anyone on your team.
Figure 1: The All Applications view displays all applications in your cluster.
In the following sections, we will cover some key components of the All Applications view:
Search, Status Timeline, and Status Frequency
The Search feature supports several app level and a process level query. Refer to Search for detailed information.
The Status Timeline represents a snapshot of all applications that are either running or completed running (failed or successful) within a certain timeframe. The x-axis is the amount of applications, while the y-axis is time. By clicking on a specific time in the bar graph, you can view the specific time length for the application that is running or has successfully ran.
The Status Frequency graph displays the amount of times (x-axis) an application with the same name (y-axis) successfully ran, stopped, or failed.
Filter Cascading application runs
There are multiple ways to query the list of applications. They incude:
By Teams - Click Team: All teams menu to display the drop-down menu that lists all teams. Scroll down and select the desired team name. Click Teams for more information on using the Teams feature.
All status sets - Click All Status Sets icon to display the drop-down menu of specific states of the application. Scroll down and select the desired status.
In the Pre-defined status set, the following filters are available:
-
Active states - Applications that are currently running.
-
Finished states - Applications that are currently finished (completed successfully).
-
Error states - Applications that are currently stopped (or never started) because of errors.
In the Individual status set, the following filters are available:
-
Pending - The application is pending to be submitted.
-
Started - The application has started.
-
Submitted - The application is submitted for running.
-
Running - The application is currently running.
-
Successful - The application has successfully run.
-
Failed - The application failed to run due to errors.
-
Stopped - The application has stopped.
|
Note
|
The Warning icon  is used for various conditions, from alerting you that your Driven Server Elasticsearch
schema has changed in Driven to your Cascading application being unresponsive.
|
By date of completion - Click All Dates icon to display the drop-down menu of set timeframes. Scroll down and select the desired timeframe.
Track Cascading applications by various metrics
Depending on the class of monitoring or class of problems that you are trying to solve, Driven lets you customize the fields for tracking the application.
As default, the metrics for applications are:
-
Status - The status state of the application (Pending, Started, Submitted, Running, Successful, Failed, and Stopped)
-
Name - The name of your Cascading application.
-
Owner - The owner (by name) of the application.
-
Pending Time - The date and time that the application is in the pending status state.
-
Run Time - The date and time that the application is in run time.
-
Finished Time - The date and time that application finished running.
-
Slice Rate - The aggregated count of a specific activity (RUNNING) measured in time. The slice rate is depicted by the rising/falling line which can change during the application runtime. The count is displayed to indicate how many slices are running at a certain time.
-
Timeline - A comprehensive timeline (in months intervals) that the application started and finished.
Figure 2: This is an example of monitoring Cascading application by certain metrics.
|
Note
|
Click semantics for the timing counters for more information. |
You can also track application-specific counters. This can become useful if you want to track application-level metrics in your Cascading application, such as the number of transactions or accounts processed.
Using Counters with a Cascading application
Counters are present at all levels of a Cascading application. To understand counters and its usage, refer to the following:
It is possible to create custom counters in Cascading. You can also use a counter as a function. Refer to the following for more information: