Cloudera Enterprise 6.3.x | Other versions

Getting Started with Cloudera Navigator

Cloudera Navigator features and functions are available through the Cloudera Navigator console, a web-based user interface provided by the host configured with the Navigator Metadata Server role (daemon). The Cloudera Navigator console invokes the REST APIs exposed by the web service provided by the Navigator Metadata Server role instance. The APIs can be called directly by in-house, third-party, and other developers who want to further automate tasks or implement functionality not currently provided by the Cloudera Navigator console. This topic discusses both of these interfaces to the Cloudera Navigator metadata component.

Note: Navigator Metadata Server is one of the roles (daemons) that comprises Cloudera Navigator. The other role is Navigator Audit Server. See Cloudera Navigator Data Management for details.

The following steps assume that the Cloudera Navigator data management component is running, and that you know the host name and port of the node in the cluster configured with the Navigator Metadata Server role. See Cloudera Installation and Cloudera Administration guides for more information about setting up Cloudera Navigator.

Continue reading:

Cloudera Navigator Console
Cloudera Navigator APIs
- Using Debug Mode

Cloudera Navigator Console

The Cloudera Navigator console is the web-based user interface that provides data stewards, compliance groups, auditing teams, data engineers, and other business users access to Cloudera Navigator features and functions.

The Cloudera Navigator console provides a unified view of auditing, lineage, and other metadata management capabilities across all clusters managed by a given Cloudera Manager instance. That is, if the Cloudera Manager instance manages five clusters, the Cloudera Navigator console can obtain auditing, lineage, and other metadata for the same five clusters. Cloudera Navigator uses its technical metadata gathering feature to keep track of which cluster originates the data.

Accessing the Cloudera Navigator Console

Open the Cloudera Navigator console in a browser at port 7187 on the host where the Navigator Metadata Server instance is running:

http://fqdn-1.example.com:7187/login.html

In this example, node 1 of the cluster is running the Navigator Metadata Server role, hosted on the default port 7187. The login page displays. Log in to the Cloudera Navigator console using the credentials assigned by your administrator.

Cloudera Manager users with the role of Navigator Administrator (or Full Administrator) can also access Cloudera Navigator console from the Cloudera Manager Admin Console.

From the Cloudera Manager Admin Console:

Open your browser.
Navigate to the Cloudera Manager Admin Console.
Log in as either Navigator Administrator or Full Administrator.
From the menu, select Clusters > Cluster-n.
Select Cloudera Navigator from the menu.
Log in to the Cloudera Navigator console.

Menu and Icon Overview

The Cloudera Navigator console opens to an empty Search results page and displays the following menu bar.

The user_name and Help menus display for all users. However, other available menu choices depend on the Cloudera Navigator user role of the logged in account. In this example, the admin account is logged in. That account has Navigator Administrator privileges which means that all menu items display and the user has full access to all system features. For a user account limited to Policy Editor privileges, only the Policies menu item displays.

This table provides a reference to all menu choices.

Icon or menu	Description
Search	Displays sets of filters that can be applied to find specific entities by source type, type, owner, cluster name, and tags.
Audits	Displays summary list of current audit events for the selected filter. Define filters for audit events, create reports based on selected time frames and filters, export selected audit details as CSV or JSON files.
Analytics	Menu for HDFS Analytics and Data Stewardship Analytics selections. This is your entry point for several dashboards that display the overall state of cluster data and usage trends: Data Stewardship Analytics displays Dashboard and Data Explorer tabs. HDFS Analytics displays Metadata and Audit tabs.
Policies	Displays a list of existing policies and enables you to create new policies.
Administration	Displays tabs for Managed Metadata, Role Management, and Purge schedule settings.
`user_name`	Displays account (admin, for example) currently logged in to Cloudera Navigator. Menu for Command Actions, My Roles, Enable Debug Mode, and Logout selections.
	Help icon and menu. Provides access to Help, API Documentation, and About selections. Select Help to display Cloudera Navigator documentation. Select About to display version information.

This is just an overview of the menu labels in the Cloudera Navigator console and pointers to some of the sub-menus. See the Cloudera Navigator Data Management guide for details.

Displaying Documentation

You can open the Cloudera Data Management guide from the Cloudera Navigator console from the Help menu.

Note: You can also view the Cloudera Data Management guide outside the scope of a running instance of Cloudera Navigator.

Displaying Version Information

To display the version and build number for the Cloudera Navigator data management component, click About in the menu.

The versions for both Cloudera Navigator and the associated Cloudera Manager instance display.

Cloudera Navigator APIs

Cloudera Navigator exposes REST APIs on the host running the Navigator Metadata Server role. In-house, third-party, and other developers can use the APIs to provide functionality not currently available through the Cloudera Navigator console or to customize their users' experience.

The APIs are used by the Cloudera Navigator console at runtime as users interact with the system. The Cloudera Navigator console has a debug mode that captures API calls and responses to a file that can then be downloaded and analyzed. See Using Debug Mode for details.

Documentation and a brief tutorial for the Cloudera Navigator APIs are available on the same node of the cluster that runs the Navigator Metadata Server role. These are also accessible from the Cloudera Navigator console. Example pathnames for direct access (outside the Cloudera Navigator console) are shown in the table.

Resource	Default location
APIs	http://`navigator-host:port`/api/v`n/operation`
API Documentation	http://`navigator-host:port`/api-console/index.html
API Usage Tutorial	http://`navigator-host:port`/api-console/tutorial.html

Operations on the API are invoked using the following general pattern:

http://navigator-host:port/api/vn/operation

The n in vn for the APIs represents the version number, for example, v11 for the Cloudera Navigator version 2.11.x. The API version number is located at the bottom of the Cloudera Navigator API documentation page.

The API uses HTTP Basic Authentication and accepts the same users and credentials that have access to the Cloudera Navigator console.

The resources listed in the table are aimed at technical and general audiences for Cloudera Navigator Data Management. The GitHub repository is aimed at developers.

Resource	Default location
GitHub cloudera/navigator-sdk	Cloudera Navigator SDK is a client library that provides functionality to help users extract metadata from Navigator and to enrich the metadata in Navigator with custom metadata models, entities, and relationships.
Cloudera Community Data Management forum	Cloudera Community > Data Management > Data Discovery, Optimization forum for Cloudera Navigator users and developers.
Cloudera Engineering Blog	In-depth technical content provided by Cloudera engineers about components and specific subject areas.

Using Debug Mode

Cloudera Navigator console debug mode captures API responses and requests during interaction with the server. Use debug mode to facilitate development efforts or when asked by Cloudera Support to troubleshoot issues.

Tip: Exploring debug files can be a good way to learn about the APIs.

To follow these steps you must be logged in to the Cloudera Navigator console.

Use Debug Mode to Collect Files for Troubleshooting

The general process for obtaining debug files to send to Cloudera Support is as follows:

Navigate to the Cloudera Navigator console menu item or page for which you want to obtain debug information.
Enable debug mode.
Reload the page and perform the specific action. For example, if you need to send a debug file to Cloudera Support for an error message that displays when you click on an entity in one of the charts, perform that action to raise the error message.
Download the debug file or files. Each time the counter changes, the content of the debug file content changes, so you should download each time the counter updates.
Disable debug mode.

Enable Debug Mode

To enable debug mode:

Log in to the Cloudera Navigator console.
Select user_name > Enable Debug Mode.
The Cloudera Navigator consoles displays a notification message in the bottom right of the page:

Notice the links to Disable and Download debug file, which you can use at any time to do either. Do not disable debug mode until you have downloaded the debug file you need.
Reload the browser page.

The counter n displays the number of API calls captured in the debug file for the current session interaction. Here is an example from a downloaded debug file showing one of the responses after reloading the page:

Download Debug File or Files

As you perform actions with the Cloudera Navigator console, the counter refreshes and keeps tracks of current calls only (stateless nature of REST). In other words, download the debug file for any given action or selection that you want to examine.

To download the debug file:

Enable Debug Mode if you haven't already.
Click the Download debug file link in the debug-enabled notification message, bottom right corner of the page.
Save the file to your local workstation.

Debug files use a naming convention that includes the prefix "api-data" followed by the name of the host and the UTC timestamp of the download time and the JSON file extension. The pattern is as follows:

api-data-navigator-host-yyyy-mm-ddThh-mm-ss.json

For example:

api-data-node01.example.com-2017-06-15T09-00-32.json

Disable Debug Mode

When you are finished capturing and downloading debug files, you can disable debug mode.

Click the Disable debug mode link in the notification message box.

The message box is dismissed and debug mode is disabled.

Or, use the Cloudera Navigator console menu:

Select user_name > Disable Debug Mode.

Set Debug Logging Levels

The Cloudera Navigator Debug Mode allows you to configure the logging levels for individual methods in the application code. For example, to increase the logging detail for API calls, you would set the logging level for the org.apache.cxf.interceptor class to "DEBUG" level. If you are collecting debugging information for a specific issue, Cloudera support will provide the class name.

To set the logging level for a Cloudera Navigator application class:

Log in to the Cloudera Navigator console.
Add /debug to the Navigator URL:
```
http://navigator-host:7187/debug
```
The debugging console appears.
Click Configure Logging.
In the Logger drop-down menu, select a Navigator class, such as org.apache.cxf.interceptor for API calls.
Set the logging level for the class.
For example, for the API call logging, select DEBUG.
Click Submit.

When changed in Debug Mode, logging levels will return to their default values after restarting the Navigator Metadata Server. To permanently change the logging levels, use Cloudera Manager to add an entry in the Navigator Metadata Server Logging Advanced Configuration Snippet. Create the entry as follows:

log4j.logger.<classname>=<level>

For example, to set the API logging level to "DEBUG", include the following string in the Advanced Configuration Snippet:

log4j.logger.org.apache.cxf.interceptor=DEBUG

See Modifying Configuration Properties Using Cloudera Manager.

Page generated August 29, 2019.