Since the monitoring console in distributed mode adds all instances as search peers to the instance hosting the monitoring console, this is a useful instance to generate diags from.Ĭhoose which files to include in your diagsĬhoose which directories are included with components. If you are on a search head and cannot generate a diag for one of your remote instances, try again from your monitoring console.
Typically, the self-hosted instances are forwarders. Splunk Cloud customers can generate diag files for self-hosted instances only. A search head that is the only search head in a deployment.Generating diags in Splunk Web is supported for a remote instance that has at least one of the following server roles: Log into Splunk Web on a search head or monitoring console in your deployment.ĭecide which instance to use to generate diags.To generate and view diags in Splunk Web, you need the get_diag capability.įollow these steps to access the Splunk Web diag generation page. After you have diags on your local machine, you can upload them to an existing Support case. You can manage previously created diag bundles, including deleting files, viewing the status of diag creation, and downloading diags to your local machine. You can recreate a diag using settings you chose in the past. You can select multiple instances in your deployment to generate diags for, and which configurations to use. Generate diags using Splunk WebĪs a Splunk Enterprise admin, you can generate diags across your deployment using Splunk Web. We cannot guarantee compliance with your company security policy.
The diag collection process attempts to exclude sensitive information from any output when using the commands below, and in any anonymized data samples sent to Splunk Support. You can review your diag file before sending it to support and ensure that no proprietary data is included.
For additional anonymization options to use on a diag file, see Anonymize data samples to send to Support. In some environments, custom app objects such as lookup tables might contain sensitive data. You can use the Splunk Enterprise command line or Splunk Web to initiate the diag collection process. The diag collection process does not collect or store any indexed data. A diag collection also includes the contents of the $SPLUNK_HOME installation path, such as app configurations, internal log files, and index metadata. The diag collection process gathers information such as server specifications, operating system (OS) version, file system information, and current network connections.
Windows memory diag command software#
When you contact Splunk support for assistance with Splunk software, they often request a diagnostic (diag) file to assist them in troubleshooting the issue.Ī diag file provides a snapshot of the configurations and logs from the Splunk software along with select information about the platform instance.
0 kommentar(er)
