This command creates a support bundle.
supportbundle create --prefix PREFIX [--preset PRESET] [--start-time TIME] [--end-time TIME] [--obfuscated] [--aggregated] [--cnodes-only]|[dnodes-only] [--cnode-ids CNODE_IDs] [--dnode-ids DNODE_IDs] [--vippool-ids VIPPOOL_IDs] [--hubble-args ARGs] [--astron-args ARGs] [--max-size SIZE] [--text] [--send-now] [--upload-via-vms] [--bucket-name NAME] [--access-key KEY] [--secret-key KEY] [--bucket-subdir DIR] [--delete-after-send]
|
Enter an identifying label to include in the bundle file name. The prefix can contain up to 64 characters. Special characters are not allowed. The name of the bundle will be bundle-<preset>-<cluster name>-<prefix>-<timestamp>.tar, where <prefix> is the prefix specified here. For example, if the prefix is MyUrgentIssue, a bundle using the mini preset created at exactly 7:45 am UTC on 3rd September 2020 on a cluster called cluster1 would be named bundle-mini-cluster1-MyUrgentIssue-2020-09-03-074500.tar. |
Select the best preset for the issue. Each preset defines a set of data objects to collect for a different type of issue. Verify with your support engineer which preset is suitable for your needs. By default, only management logs are collected. Specify one of the following presets as PRESET:
|
|
|
Sets the start time from which to collect information. Specify TIME in UTC+0 in the format |
|
Sets the end time for the period to collect information. Specify TIME in UTC+0 in the format It's usually advisable to consult with the support engineer on the time frame so that you can make it as short as possible and minimize the size of the bundle. |
|
Converts all bundled objects to text and obfuscates them. Any data that cannot be converted to text is not included in the bundle. The following types of information are replaced with a non-reversible hash: file and directory names, IP addresses, host names, user names, passwords, MAC addresses. If this option is not specified (default), the information is not obfuscated. |
Saves an aggregated bundle file on the management CNode. If this option is not specified (default), a separate bundle file is created on each CNode and DNode that is included in the bundle. The aggregated file is created in addition to the separate bundle files per node. It supplies all the information in one larger file. Unlike the separate bundle files, an aggregated bundle is not overwritten when a new support bundle is created. |
|
|
Specify this option to collect data from CNodes only. |
|
Specify this option to collect data from DNodes only. |
|
Specify a comma-separated list of CNode IDs to collect data from. By default, all CNodes are included. This option cannot be used together with |
|
Specify a comma-separated list of DNode IDs to collect data from. By default, all DNodes are included. This option cannot be used together with |
|
Specify a comma-separated list of VIP pools to collect data only from CNodes that are included in these VIP pools. |
|
Enter any arguments to pass to Hubble, per instructions from the support engineer. |
|
Enter any arguments to pass to Astron, per instructions from the support engineer. |
|
Enter a maximum data limit to apply to the collection of binary trace files, in GB. You can use this option to limit the overall size of the support bundle. |
|
Converts all bundled objects to a text format. Any data that cannot be converted to text is not included in the bundle. This setting is enabled automatically if |
|
Sends the support bundle immediately. |
|
Uploads a non-aggregated support bundle via VMS. Otherwise, the upload is done from each node. This option is available only if Using this option requires a proxy to be configured with the |
|
Specifies the S3 bucket name of the destination S3 bucket. |
|
Specifies the access key of a valid key pair to access the destination S3 bucket. |
|
Specifies the secret key of a valid key pair to access the destination S3 bucket. |
|
Specifies the subdirectory in the destination S3 bucket to which to upload the support bundle. |
|
Deletes the support bundle immediately after it has been sent successfully. |
Comments
0 comments
Article is closed for comments.