Generating a VM-based diagnostic bundle (TP)

The collect-<resource-type>-diagnostics commands trigger log collection. You need to provide a CRN of a resource (Data Lake, FreeIPA, or Data Hub cluster), a description, and a destination for the bundle. The generated bundle can be saved to cloud storage or to a local file. The command progress (including the location where the bundle is generated) is printed in the Event History tab on the UI.

Note: This feature only works out of the box with environments created or upgraded in October 2020 or later. If your environment is older and your nodes have internet access, you can use the --update-package option to download the newest library that is needed for the collection.

Prerequisites

If you would like to use cloud storage as a destination, ensure that the Logger and IDBroker instance profiles (on AWS) or managed identities (on Azure) are able to write to the specified cloud storage location.

Example commands

To run collection with salt script included and update cdp-telemetry package on the nodes, use one of the following commands, Replace <DESCRIPTION> with an actual description and the <DATAHUBCRN> with an actual CRN:

cdp environments collect-freeipa-diagnostics --environment-name <NAME-OR-CRN> \
--description <DESCRIPTION> \
--destination CLOUD_STORAGE \
--update-package \
--include-salt-logs

cdp datalake collect-datalake-diagnostics --crn <datalakecrn> \
--description <DESCRIPTION> \
--destination CLOUD_STORAGE \
--update-package \
--include-salt-logs

cdp datahub collect-datahub-diagnostics --crn <DATAHUBCRN> \
--description <DESCRIPTION> \
--destination CLOUD_STORAGE \
--update-package \
--include-salt-logs

To collect only specific custom logs (such as /var/log/audit/audit.log used in this example), use:

cdp environments collect-freeipa-diagnostics --environment-name <name> \
--description <DESCRIPTION> 
--destination CLOUD_STORAGE \
--additional-logs path=/var/log/audit/audit.log,label=audit \
--labels audit

If you run this command:

• Logs specified under --additional-logs will be collected

• Due to the specified label, all other logs will be filtered out and no other logs will be included in the bundle.

Required parameters

--environment-name (for Data Lake or Data Hub) or --crn (for Data Hub)Provide a CRN of your Data Lake, FreeIPA, or Data Hub cluster. You can obtain it by running a list or describe command on your resource.

--description Provide a description for the diagnostics bundle.

--destination Specify a destination of the diagnostics collection: CLOUD_STORAGE, or LOCAL:

• CLOUD_STORAGE: Saves collected diagnostics into a tar.gzfile file and uploads it to your logs cloud storage location specified during environment registration, to a PATH that looks like this:

   cluster-logs/<CLUSTER-TYPE>/<CLUSTER-NAME>_<UUID PART-OF-CLUSTER-CRN>/diagnostics.     

  The “cluster logs” directory is only created if your cloud storage location is a bucket. If your cloud storage location includes a directory within a bucket, then the “cluster logs” directory is not created.

• LOCAL: Diagnostics will be collected to a compressed file, and saved to /var/lib/filecollector on every cluster node.

Optional parameters

--labels You can use this to pass a list of labels that can be used to filter collected logs. This is useful if instead of including all logs, you would only include certain specific logs in the bundle. This list can be obtained from the get-<cluster-type>-log-descriptors response.

--additional-logs One or more additional VM log objects that will be included in the diagnostics bundle. A VM log object is a path/label pair. Cloudera support may ask you to provide specific values here.

--include-salt-logs If this is set, salt minion/master logs will be included in the diagnostic bundle.

--case-number Allows you to provide a support case number.

--update-package If this is set, during diagnostics collection, the required third party applications will be downloaded and updated on the VM nodes. This requires internet access.

--storage-validation You can use this if using CLOUD_STORAGE as a destination. If this is set, cloud storage write validation check will happen during an initial phase of the diagnostics collection.