Driven User Guide: Configuring Teams for Collaborationversion 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.2. Team Details
- 7. Using 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
Applications are not deployed and monitored in isolation. Usually, application development is a collaboration between the IT administrators and developers, engineering, business analysts, and other data scientists. When applications become operational, it becomes vital to create collaboration to investigate job behavior and observe characteristics. Organizing application execution data by groups of stakeholders can help you and your colleagues focus on metrics that you are targeting.
On the other hand, most organizations want to categorize and restrict viewing of application metrics for governance, regulatory compliance, developing models for chargebacks, or other reasons. For example, in a bank you may have the Hadoop production cluster as a single enterprise capability, shared between different lines of businesses such as marketing, fraud, operational risk, and across organizations in different geographies. The bank runs many applications that contain confidential data. In this scenario, it is possible that information about the xyz application should be revealed only to the fraud and operational risk business units because the xyz application processes confidential data that needs to be monitored by these units.
Using teams, you can both share and restrict views of specific application metrics. In Driven a team is associated with an API key. For any application using the API key, the data from the application is visible only to users who are team members and to Driven administrators. As a result, when a team member saves a status or application view with programmed API keys, the view is accessible to other team members and the Driven administrator.
|For the sake of comparing multiple applications that are restricted by teams, you might need a user with administrator privileges to perform this analysis efficiently, or to configure the discoverability and visibility settings on those teams. For more information, see Application Execution Detail Access|
Access a team view by clicking Teams from the header and selecting one of the links that appear in that section. Alternatively, hover over Teams and select a team from the drop-down menu.
By default, a user who creates a team is the team leader. However, the default team leader can transfer the role to another user on the team. Team leaders can also invite users to join the team, remove users, and delete the team altogether.
The following procedure permits users who are not logged in to Driven as an administrator to create a team and assign existing user accounts to the team. See Using the Driven Admin Console in the Driven Administrator Guide for more information about administrator configuration of teams and users.
Perform the following tasks to create a team:
Click Teams in the Global Navigation.
Click the Create Team button in the Teams table.
Enter a name for your team. The newly created team will appear in the Teams table. By default you will become Team Leader of your newly created team.
Record or copy the API key that appears next to the newly created team. You need this to configure the Driven Plugin to display application run data to Driven users who belong to the team with the API key.
In the Teams table, click on the team name of the team you wish to view the details of. If you are a Driven Admin or are the Team Leader of the team you are viewing, you have options to configure the different aspects of the team. As a regular team member, the information is read only.
Application Execution Detail Access
External Issue Tracking
Webhook Connections and Email Notifications
The team details page is the place where you can manage other aspects of the team, such as deleting a team from Driven.
If you are are a Driven Admin or the Team Leader, you can click on the Edit Team Name, Change Leader, and Delete Team buttons to perform their respective operations.
The Discoverability setting determines who can see this team’s apps in search results. The Visibility setting determines who has access to view this team’s applications' details.
These are all of the members of the team. If you are a Driven Admin or are Team Leader, you can add Driven users directly to the team, or remove members from the team.
To add members to the team, click the Add Member(s) button in the Members table. Choose the user(s) you would like add to the team, and click the Submit button.
To remove members from the team, choose the member(s) you would like to remove, and click the Remove Member(s) button in the Members table. You will be prompted to confirm that you would like to remove the selected members. Click the Remove button to proceed.