Connecting Cloudera Manager to Workload XM

Diagnostic information about job and query execution is sent to Workload Experience Manager (Workload XM) with Telemetry Publisher, a role in the Cloudera Manager Management Service. When new clusters are added with Cloudera Manager, Telemetry Publisher automatically sends the new cluster information to Workload XM. This topic describes how to connect Cloudera Manager to Workload XM by connecting the Cloudera Manager Telemetry Publisher service role to a Cloudera Altus account.

Connecting Cloudera Manager Telemetry Publisher to Workload XM is a three-step process.

After connecting Cloudera Manager to Workload XM, you must enable Log and Query Redaction for the Telemetry Publisher Service. If you must use a proxy server with Workload XM, see Configuring Telemetry Publisher to Use a Proxy Server.

Step 1. Get Altus Credentials

In order to use Workload XM, you need an Altus account. For more information about how to set up an Altus account, see the Cloudera Altus documentation.

  1. Go to wxm.cloudera.com, and follow the prompts to set up your account.
  2. On the Altus Home page, click on your user name in the upper right corner of the page, and select My Account.
  3. Click Generate Access Key. This creates an Altus Access Key ID and Altus Private Key.

    The Altus Access Key ID and Altus Private Key are needed to add an Altus account to Cloudera Manager.

Step 2. Add Altus Credentials to Cloudera Manager

  1. Sign in to the Cloudera Manager Admin Console.
  2. Navigate to Administration > External Accounts > Altus Credentials.
  3. Select Add Access Key Authentication, provide the following information, and click Add:
    • Name
    • Altus Access Key ID
    • Altus Private Key
  4. Navigate to Administration > Settings. Type Altus in the search box to find the Telemetry Altus Account configuration setting. Then select the Altus credentials you created and named in Step 3.
  5. Click Save Changes.

Step 3. Add the Telemetry Publisher Service Role

After you add an Altus account, add the Telemetry Publisher service role to the Cloudera Manager Service.

  1. In the Cloudera Manager Admin Console, navigate to Clusters > Cloudera Management Service.
  2. Select Actions > Add Role Instances. The Add Role Instances wizard opens.

    If a Telemetry Publisher role already exists, Cloudera Manager does not let you add another.

  3. Select a host for the Telemetry Publisher and complete the wizard.
  4. If you are using Java 8, skip this step.
    If you are using Java 7, you must configure Telemetry Publisher as follows:
    1. In the Cloudera Manager Admin Console, click Cloudera Management Service.
    2. On the Cloudera Management Service page, select the Configuration tab and then select the Telemetry Publisher filter under Scope.
    3. Type java configuration in the search text box to locate the Java Configuration Options for Telemetry Publisher configuration property and add the following to the text box:

      -Dhttps.protocols=TLSv1.2 -Dhttps.cipherSuites=TLS_RSA_WITH_AES_256_CBC_SHA256
                        
      Java 7 Configuration for Telemetry Publisher

    4. Click Save Changes.
  5. Go to Clusters > Cloudera Management Service and select the Telemetry Publisher role.
  6. Click Actions > Test Altus Connection. A successful test indicates that the Telemetry Publisher can connect to Altus.
  7. Go to Clusters > Hive> > Instances and restart the roles for Hive.

Log and Query Redaction for the Telemetry Publisher Service

Log and query redaction for the Telemetry Publisher service is controlled with the Log and Query Redaction configuration property. This property is enabled by default and works with the log and query redaction property for HDFS. If you want to disable log and query redaction for the Telemetry Publisher service, you must also disable log and query redaction for HDFS or the Telemetry Publisher service will not start.

The Log and Query Redaction configuration property is only available in Cloudera Manager version 5.16 and later. For more information about log and query redaction, see the Cloudera Manager documentation.

If you must disable Telemetry Publisher log and query redaction for testing purposes:

  1. In the Cloudera Manager Admin Console, navigate to Clusters > HDFS > Configuration, and type redact into the Search box to locate the log and query redaction properties for HDFS.
  2. Uncheck the Enable Log and Query Redaction property, and then click Save Changes.
  3. Still in the Cloudera Manager Admin Console, click Clusters > Cloudera Management Service > Configuration > Telemetry Publisher, type redact in the Search box, and uncheck the Log and Query Redaction property for the Telemetry Publisher Default Group:



  4. Click Save Changes.
  5. Restart both the HDFS and the Telemetry Publisher services to disable log and query redaction.

Configuring Telemetry Publisher to Use a Proxy Server

You can configure the Telemetry Publisher service to send metrics as well as configuration and log files to WXM by way of a proxy server for database and Altus metrics uploads. You cannot upload information from Amazon Web Services (AWS) by way of a proxy server. By default, this configuration property is disabled.

Telemetry Publisher uses the TLS/HTTPS protocol to send telemetry information to WXM. This ensures that the data is encrypted in flight. The proxy you use must support the HTTP CONNECT method in order to be able to pass through the encrypted messages. For more information, see the associated RFC.

Telemetry Publisher support for proxy servers is only available in Cloudera Manager version 5.16 and later.

To enable Telemetry Publisher to send information by way of a proxy server:

  1. In the Cloudera Manager Admin Console, navigator to Clusters > Cloudera Management Service > Configuration > Telemetry Publisher, and type proxy into the Search box to locate the proxy configuration properties:



  2. Select Telemetry Publisher Default Group and provide the proxy server name, port, username, and password.
  3. Click Save Changes, and then restart the Telemetry Publisher service.