Driven User Guide: Managing Applications with Tags
version 2.2.6- 1. Overview of Monitored Applications
-
1.1. Logging In
1.2. Status Views
- 2. Searches, Saved Views, and Accessing Relevant Data
-
2.1. Starting a Search
2.3. My Teams Views
2.5. Customizing Searches
2.6. Periodic Views
- 3. Using the App Details Page
-
3.4. Viewing the Graph
3.6. Details Table
- 4. Understanding the Unit of Work Details Page
- 5. Managing Applications with Tags
- 6. Configuring Teams for Collaboration
-
6.1. Creating and Managing Teams
6.2. Team Details
- 7. Using Annotations
-
7.1. Creating Custom Annotations
7.2. Data Visibility
- 8. Execute Hive Queries as Cascading HiveFlow
-
8.1. Using HiveFlow
8.2. Driven for HiveFlow
- 9. Execute Cascading MapReduce Flows
- 10. User Profile
-
10.1. User Actions
10.2. User Credentials
10.3. User Statistics
10.4. Invitations
10.5. Teams
Managing Applications with Tags
|
Tip
|
Application developers and Driven system administrators should collaborate to form a consistent and logical taxonomy for tags. Tagging helps segment applications because tags can be used as search and column-chooser parameters. |
Tags are labels that can be applied to applications for categorization so that Driven users can sort and retrieve data more easily. For example, by creating a series of tags based on business units and assigning them to the applications that pertain to business units, developers can help Driven users track applications that are associated with each unit.
The tagging feature allows you to manage your data processing and ETL flows in a manner to provide superior support for governance, compliance, and operational visibility. While tags extend the value of the Driven user interface, tags are created and assigned during application development or Driven Plugin configuration.
Best Practice for Tags
A tag should consist of a category label and a term that identifies a particular
entity in the category. Another way to think of tag construction is naming a
dimension and then identifying a particular value of the dimension. For example,
a couple tags in a sequence could be department:accounting and
department:security.
Always use the colon, without spaces, to separate the label and value.
Assigning Tags as Application-Level Properties
As a Cascading application developer, you can assign a tag or group of tags to the application. Enter the following command, replacing the terms in "country:Canada" with your own:
AppProps.addApplicationTag(properties, "country:Canada");To define multiple tags, enter tag terms as comma-separated values.
For users of the Driven Agent with Hive and MapReduce refer to Driven Agent Guide for how to use agent properties to send tags for the specific platform.
Assigning Tags in the Driven Plugin Configuration File
If you have privileges to edit the Driven Plugin configuration file, you can specify a tag or group of tags for applications that run based on settings in the cascading-service.properties file. See Driven Plugin Guide for more information.
Using Tags in a Search Query
Tags also allow you to quickly find your application with search queries. If you run a search query with a valid tag name, Driven displays the applications that are associated with the tag.
Finding Tagged Applications with the Column Chooser
If you want to see which applications in a table are associated with a tag, select the tag category label in the column chooser. The tag label that you select appears as a column in the table. An application that is tagged with the label displays the tag value term in the cell of the column.
For example, Sorting applications in a view by tags (runid:fd33b2 and process:app) shows applications that are tagged runid:fd33b2 and process:app. The cluster, runid, and process columns appear in the table because the user selected these tag prefixes in the column chooser.
