Generate a diagnostic file
To help diagnose a problem, Splunk Support might request a diagnostic file from you. Diag files give Support insight into how an instance is configured and how it has been operating up to the point that the diag command was issued.
Diag generation, whether in Splunk Web or at the command line, collects basic information about your Splunk platform instance, including Splunk platform configuration details. It gathers information, such as server specs, OS version, file system, and current open connections, from the machine running the Splunk platform. From the Splunk platform instance, it collects the contents of
$SPLUNK_HOME such as app configurations, internal Splunk log files, and index metadata.
Diags do not contain any of your indexed data. You can examine the diag file to ensure that no proprietary data is included. In some environments, custom app objects, like lookup tables, can contain sensitive data. Read on for more details about controlling the files contained in a diag.
Note: Before you send any files or information to Splunk Support, verify that you are comfortable sending it to us. The Splunk platform tries to exclude sensitive information from any output from the commands below and in Anonymize data samples to send to Support, but we cannot guarantee compliance with your particular security policy.
Generate diags using Splunk Web
As a Splunk Enterprise admin, you can generate diags across your deployment using Splunk Web.
You can select multiple instances in your deployment to generate diags for, and which configurations to use. You can recreate a diag using settings you chose in the past. You can manage previously created diag bundles, including deleting files, viewing the status of diag creation, and downloading diags to your local machine. After you have diags on your local machine, you can upload them to an existing Support case.
To generate and view diags in Splunk Web, you need the
Follow these steps to access the Splunk Web diag generation page.
- Log into Splunk Web on a search head or monitoring console in your deployment.
- Click Settings > Instrumentation.
Decide which instance to use to generate diags
Generating diags in Splunk Web is supported for a remote instance that has at least one of the following server roles:
- A search head that is the only search head in a deployment.
- A clustered search head.
- A clustered indexer.
- An indexer cluster master.
If you are on a search head and cannot generate a diag for one of your remote instances, try again from your monitoring console. 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.
Choose which files to include in your diags
Choose which directories are included with components. By default, all components are included but REST. You can adjust the thoroughness with which some components are collected by using additional options. See Include or exclude content using components.
Components and options you select in Splunk Web override any local settings.
Generating a diag in Splunk Web requires Splunk Enterprise version 7.1.0 or later. In addition, the indexers in your deployment must be running Splunk Enterprise version 6.5.0 or later. Generating a diag on a remote instance using Splunk Web requires the remote instance to be running a minimum Splunk Enterprise version as follows.
|Task||Minimum Splunk Enterprise version for remote instance|
|Generate a diag of any remote instance, except a cluster master||6.0|
|Generate a diag of a cluster master||7.1.0|
|Use component granularity on a remote instance*||7.1.0|
|Exclude lookups by default||6.5.0|
* If you generate a diag on an instance running Splunk Enterprise versions earlier than 7.1.0, all components are requested, except REST. You can, however, use Exclude and All dumps.
How diags are generated and stored in your deployment
Diags are stored in the
$SPLUNK_HOME path. If you run the diag command to generate a diag on a remote instance, the diag artifacts are transferred to the instance where the command was invoked.
Run diag at the command line
Be sure to run diag as a user with appropriate access to read Splunk files.
The basic syntax to run diag at the command line is as follows.
If you have difficulty running diag in your environment, you can also run the python script directly from the bin directory using cmd.
./splunk cmd python $SPLUNK_HOME/lib/python2.7/site-packages/splunk/clilib/info_gather.py
splunk cmd python %SPLUNK_HOME%\Python-2.7\Lib\site-packages\splunk\clilib\info_gather.py
The Python version number might differ in future versions of Splunk Enterprise, affecting this path.
diag-<server name>-<date>.tar.gz in your Splunk home directory, which you can upload to your Splunk Support case via the website or built-in upload functionality. If your Support case is about forwarding, Support will probably need a diag for both your forwarder and your receiver. Label each diag so it is clear which is from the forwarder and which is from the receiver.
Exclude files from diag
The Splunk platform can be told to leave some files out of the diag. One way to do this is with path exclusions. In Splunk Web, use the Exclude patterns option. At the command line you can use the
--exclude flag. For example:
splunk diag --exclude "*/passwd"
This is repeatable:
splunk diag --exclude "*/passwd" --exclude "*/dispatch/*"
Files excluded by the
--exclude feature are listed in
excluded_filelist.txt in the diag bundle to ensure Splunk Support can interpret the diag.
Include or exclude content using components
A more robust way to exclude content is with components. The following options select which categories of information should be collected.
--collect=<list> Declare a set of components to gather, as a comma-separated list, overriding any prior choices --enable=<component_name> Add a component to the work list --disable=<component_name> Remove a component from the work list
The following components are available at both the command line and in Splunk Web.
|conf_replication_summary||A directory listing of replication summaries produced by search head clustering. This component is not available in Splunk Web.|
|consensus||Copies of the consensus protocol files used for search head cluster member coordination from var/run/splunk/_raft|
|dispatch||The search dispatch directories. See Dispatch directory and search artifacts in the Search Manual.|
|etc||The entire contents of the
|file_validate||The results of the latest file integrity check. See Check the integrity of your Splunk software files in the Admin Manual.|
|index_files||Files from the index that describe their contents. (Hosts.data, Sources.data, Sourcetypes.data, and bucketManifests). User data is not collected. If diag collects index files on larger deployments, it might take a while to run. Read about index files in the Splexicon.|
Index data file gathering level: manifests, or full, meaning manifests + metadata files. Default: manifests.
|index_listing||Directory listings of the index contents are gathered, in order to see file names, directory names, sizes, timestamps, and the like. This information is recorded in systeminfo.txt.|
Index directory listing level: light (hot buckets only), or full, meaning all index buckets. Default: light.
|kvstore||Directory listing of the Splunk key value store files.|
|log||The contents of
|pool||If search head pooling is enabled, the contents of the
||By default diag excludes lookup files in |
|rest||splunkd httpd REST endpoint gathering. Collects output of various splunkd urls into xml files to capture system state. Off by default.|
|searchpeers||Directory listing of the "searchpeers" location, actually the data provided by search*heads* on indexers/search nodes.|
|app:<app_name>||If you have an app installed that extends diag, adding apps-specific troubleshooting data, it will offer a component like this. For information on what type of data the app provides, see the app documentation, review the content stored in the produced tar file, or contact the app developers. This component is not available in Splunk Web.||An app might offer additional app-specific flags, in the form |
For example, the most commonly requested files collected are log files and configuration files only for initial analysis. To collect only those two components, use:
$SPLUNK_HOME/bin/splunk diag --collect=log,etc
Defaults can also be controlled in server.conf. Refer to server.conf.spec in the Admin Manual for more information. Apps do not currently offer defaulting of their settings in server.conf
Redact search strings
Diag by default removes some types of sensitive information from search strings in diag files. Read about configuring search string redaction in server.conf.spec.
These options cause diag to redact or hide data from the output diag.
--filter-searchstrings Attempt to redact search terms from audit.log & remote_searches.log that may be private or personally identifying --no-filter-searchstrings Do not modify audit.log & remote_searches.log
Run the diag command on a remote instance
To gather diags from remote Splunk Enterprise installations, you need:
- A local instance with Splunk Enterprise installed.
- A local login credential that has the
get_diagcapability. The admin role has this capability by default.
- A login credential for the remote Splunk Enterprise instance.
- Sufficient space to store the remote diag file locally in the
Remote diag collection does not work with universal forwarders. The options available when including or excluding components using remote diag collection are:
- Using a shell prompt, go to the folder
- Run the command
./splunk diag -uri "https://<host>:<mgmtPort>"
- When prompted, type the login credential and password
- The diag will run and the file transferred to the local Splunk Enterprise instance. Depending upon the size of the diag file and the speed of the connection, this will take time to complete.
- Using a shell prompt, go to the folder
$SPLUNK_HOMEand look for the file
Upload a file to Splunk Support
If you have a support case already open, you can attach a diag at the conclusion of generating the output. Alternatively, you can upload a file that already exists, such as a previously generated diag or other debugging data.
To generate and upload a diag, the CLI syntax is:
splunk diag --upload
To upload a file you already have, the syntax i:
splunk diag --upload-file=a-filename.zip
This command interactively prompts for values such as a splunk.com user name and password, choice of open cases for that user, and a description of the upload.
Optionally, you can perform the upload work non-interactively, by providing the required values as flags:
Upload: Flags to control uploading files Ex: splunk diag --upload [...] --case-number=case-number Case number to attach to, e.g. 200500 --upload-user=UPLOAD_USER splunk.com username to use for uploading --upload-password=UPLOAD_PASSWORD splunk.com password to use for uploading --upload-description=UPLOAD_DESCRIPTION description of file upload for Splunk support --firstchunk=chunk-number For resuming upload of a multi-part upload; select the first chunk to send
User names on splunk.com do not include @domain.com. The --firstchunk flag matters only if uploading a huge file fails after partial success. In this case, the diag output explicitly tells you the command to use to retry.
splunk diag --upload --case-number=757096 --upload-user=jawlige --upload-password=<passwd> --upload-description="Monday diag, as requested."
Diag CLI examples
Exclude a lookup table
These two examples exclude content on the file level. A lookup table can be one of several formats, like .csv, .dat, or text.
Exclude all .csv files, or all .dat files, in
splunk diag --exclude "*.csv" or
splunk diag --exclude "*.dat"
Note: These examples exclude all files of that type, not only lookup tables. If you have .csv or .dat files that will be helpful for Support in troubleshooting your issue, exclude only your lookup tables. That is, write out the files instead of using an asterisk.
Exclude the dispatch directory
This example excludes content on the component level. Exclude the dispatch directory to avoid gathering search artifacts (which can be very costly on a pooled search head):
$SPLUNK_HOME/bin/splunk diag --disable=dispatch
Exclude multiple directories
To exclude multiple components, use the
--disable flag once for each component.
Exclude the dispatch directory and all files in the shared search head pool:
$SPLUNK_HOME/bin/splunk diag --disable=dispatch --disable=pool
Note: This does not gather a full set of the configuration files in use by that instance. Such a diag is useful only for the logs gathered from
$SPLUNK_HOME/var/log/splunk. See What Splunk Enterprise logs about itself in this manual.
Gather only logs
To include only the Splunk Enterprise internal log files:
$SPLUNK_HOME/bin/splunk diag --collect=log
Generate a diag, then upload it
$SPLUNK_HOME/bin/splunk diag --upload
Fetch a diag from a remote instance, then upload it
$SPLUNK_HOME/bin/splunk diag --uri https://splunkserver.example.com:8089 $SPLUNK_HOME/bin/splunk diag --upload-file=<diag_from_prior_command>
Save the settings for diag in server.conf
You can update the default settings for diag in the
[diag] stanza of server.conf.
[diag] EXCLUDE-<class> = <glob expression> * Specifies a glob / shell pattern to be excluded from diags generated on this instance. * Example: */etc/secret_app/local/*.conf
Flags that you append to
splunk diag override server.conf settings.
Primarily, a diag contains server logs, from
$SPLUNK_HOME/var/log/introspection, and the configuration files, from
Specifically, by path name, there are:
- Files containing the state of the consensus protocol produced by search head clustering from var/run/splunk/_raft
- The generated file that splunkd uses at runtime to control its component system (pipelines & processors), from var/run/splunk/composite.xml
- A copy of all the messages diag produces to the screen when running, including progress indicators, timing, messages about files excluded by heuristic rules (eg if size heuristic, the setting and the size of the file), errors, exceptions, etc.
- A copy of some of the data from the search dispatch directory. Results files (the output of searches) are not included, nor other similar files (events/*)
- A copy of the contents of the configuration files. All files and directories under $SPLUNK_HOME/etc/auth are excluded by default.
- A list of files which diag would have included, but did not because of some restriction (exclude rule, size restriction). This is primarily to confirm the behavior of exclusion rules for customers, and to enable Splunk technical support to understand why they can't see data they are looking for.
- The log files from $SPLUNK_HOME/var/log/introspection
- The log files from $SPLUNK_HOME/var/log/splunk
- Output of several splunkd http endpoints that contain information not available in logs. File input/monitor/tailing status information, server-level admin banners, clustering status info if on a cluster.
- A single utility script may exist here for support reasons. It is identical for every diag.
- Generated output of various system commands to determine things like available memory, open splunk sockets, size of disk/filesystems, operating system version, ulimits.
- Also contained in systeminfo.txt are listings of filenames/sizes etc from a few locations.
- Some of the splunk index directories (or all of the index directories, if full listing is requested.)
- The searchpeers directory (replicated files from search heads)
- Search Head Clustering -- The summary files used in synchronization from var/run/splunk/snasphot
- Typically var/...
- The paths to the indexes are a little 'clever', attempting to resemble the paths actually in use (For example, on windows if an index is in e:\someother\largedrive, that index's files will be in e/someother/largdrive inside the diag). By default only the .bucketManifest for each index is collected.
- If you have an app installed which extends diag, the content it adds to the produced tar.gz file will be stored here.
Behavior on failure
If for some reason diag fails, it does the following:
- Cleans up temporary files it created while running.
- Leaves a copy of the output in a temporary filename it references.
rjodman@mcp:~$ splunk/bin/splunk diag [... lots of normal output...] Selected diag name of: diag-mcp-2014-09-24 Starting splunk diag... [etc .... etc] Getting index listings... Copying Splunk configuration files... Exception occurred while generating diag, we are deeply sorry. Traceback (most recent call last): File "/opt/splunk/lib/python2.7/site-packages/splunk/clilib/info_gather.py", line 1959, in main create_diag(options, log_buffer) File "/opt/splunk/lib/python2.7/site-packages/splunk/clilib/info_gather.py", line 1862, in create_diag copy_etc(options) File "/opt/splunk/lib/python2.7/site-packages/splunk/clilib/info_gather.py", line 1626, in copy_etc raise Exception("OMG!") Exception: OMG! Diag failure, writing out logged messages to '/tmp/diag-fail-F2B94h.txt', please send output + this file to either an existing or new case ; http://www.splunk.com/support We will now try to clean out the temp directory...
For most errors, the diag command tries to guess at the original problem, but it also writes out a file for use in bugfixing diag. Send this file to Support, and a workaround can often be provided quickly.
Have questions? Visit Splunk Answers and see what questions and answers the Splunk community has about diags.
Watch a video on using the diag and anonymize CLI commands by a Splunk Support engineer:
How to file a great Support case
Anonymize data samples to send to Support
This documentation applies to the following versions of Splunk® Enterprise: 7.1.0, 7.1.1, 7.1.2, 7.1.3, 7.1.4, 7.1.5, 7.1.6, 7.1.7, 7.1.8, 7.1.9, 7.1.10, 7.2.0, 7.2.1, 7.2.2, 7.2.3, 7.2.4, 7.2.5, 7.2.6, 7.2.7, 7.2.8, 7.2.9, 7.2.10
Feedback submitted, thanks!