If our support agent requests that you create a support bundle for troubleshooting purposes, follow this procedure. The bundle creation process extracts information from your cluster's logs into a file that you can send to us.
From the menu (click ), select the Support page and then select the Bundles tab.
The Create Bundle dialog appears.
Complete the fields:
Enter a unique identifier for the bundle file name. The file will be named according to a convention and will include the prefix.
Select the cluster.
Optionally specify a path for saving the bundle file on each node. If unspecified, the file is saved at
If requested by the support agent, specify a channel. If unspecified, all channels are included.
Specifies a start time for the period from which to collect logs. Limiting the collection to a specific period helps to reduce the size of the bundle and the time taken to create the bundle. Either mini, or a start-end time range must be specified
You must enter either the Start time and the End time or enable the Mini option.
Specifies an end time for the period of logs to collect. See also Start time.
Enter a Silo ID to restrict the collection to a specific module, identified by Silo ID on the Modules tab of the Support page. The support agent may request that you restrict the bundle to a specific module.
Optionally specify a minimum severity to include only logs of events with the specified severity or higher.
Optionally specify CNodes by ID, to include only the specified CNodes.
Optionally specify DNodes by ID, to include only the specified DNodes.
Optionally specify a maximum file size, in GB, if needed, to limit the size of the bundle file. Use this if you are afraid the file might take up too much disk space.
Enable to save an aggregated bundle file on the management CNode in addition to a file saved on each node.
Otherwise and by default, a file is saved on each node only.
Aggregated bundle files are given unique names and therefore not overwritten by subsequent aggregated bundle files. The separate bundle files saved on each node are saved with the same name as previous bundles at the same location and therefore overwrite the previous bundle.
Enable to send a predefined set of minimum data, if requested by the support agent.
Enable to collect dev traces.