Skip to main content
Skip table of contents

Sending Telemetry Data for Analysis

Generate and send Telemetry data to D2iQ for analysis.

For more information around the gathered data, collection purposes, and data storage location, see Telemetry.

This feature is currently not available in air-gapped environments.

Prerequisites

Generate and Send a Bundle

A telemetry bundle is tied to a specific cluster. If there is more than one cluster in your environment, run the following instructions for each cluster by providing a context for your commands. You can either use the --kubeconfig flag as shown below, or set an environment variable as shown in Provide Context for Commands with a kubeconfig File.

For more information around the gathered data, collection purposes, and data storage location, see Telemetry.

Telemetry Bundle

Execute the following command to upload a telemetry bundle for analysis:

CODE
dkp upload telemetry --bundle-profile telemetry --kubeconfig=${CLUSTER_NAME}.conf

This command automatically generates a bundle and sends it to a storage service managed by D2iQ.

This is the default profile, if no flag is set when running dkp upload telemetry.

If the upload fails due to size limitations, generate a support bundle locally, and provide it to D2iQ through a support ticket.

Alternative: Extended Bundle

See Used collectors if you want to know more about how these two bundles differ.

Execute the following command to upload an extended bundle for analysis:

CODE
dkp upload telemetry --bundle-profile diagnostics --kubeconfig=${CLUSTER_NAME}.conf

This command automatically generates a bundle and sends it to a storage service managed by D2iQ.

Recommended Telemetry Upload Frequency

The recommended frequency for data upload is every three months.

If you want to upload telemetry data on a schedule, see Scheduling Telemetry Upload for a configuration aid.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.