What Splunk logs about itself
What Splunk logs about itself
Splunk Enterprise keeps track of its activity by logging to various files in
The Splunk Enterprise internal log files are rolled based on size. You can change the default log rotation size by editing
Search these files in Splunk Web by typing:
Here is a list, with descriptions, of the internal logs in
$SPLUNK_HOME/var/log/splunk. Splunk's internal logs are useful for troubleshooting or metric analysis.
Note that some log files are not created until your Splunk instance uses them, for example crawl.log.
|Log file name||Useful for?|
|audit.log||Stats about user activity. For example, if you're looking for information about a saved search, audit.log matches the name of your saved search (savedsearch_name) with its search ID (search_id), user, and time. With the search_id, you can look up that particular search elsewhere, like in the search dispatch directory. Read about audit events in the Securing Splunk Manual.|
|btool.log||Log of btool activity. Read about btool in this manual.|
|crawl.log||Log of crawl activity. Read about crawl in the Getting Data In Manual. Crawl is now deprecated.|
|django_access.log||Django HTTP request log (equivalent to web_access.log) for the Django Bindings component of the Splunk Web Framework.|
|django_error.log||Raw Django error output from Splunk Web Framework (not really meant to be human readable). Used with link on error screens to see the full error in Splunk Web.|
|django_service.log||General Django related messages from Splunk Web Framework (equivalent to web_service.log)|
|export_metrics.log||Log of metrics related to exporting data with Hadoop Connect.|
|first_install.log||Shows version number.|
|inputs.log||Inputs found by crawl. This log file will be empty unless you use the crawl command.|
|intentions.log||Intentions activity. Read about intentions in the Developing Views and Apps for Splunk Web Manual.|
|license_audit.log||Deprecated. Look at license_usage.log instead of here.|
|license_usage.log||Indexed volume in bytes per pool, index, source, sourcetype, and host. Starting in 4.2, license_usage.log is available only on a Splunk license master.|
|metrics.log||Contains periodic snapshots of Splunk performance and system data, including information about CPU usage by internal processors and queue usage in Splunk's data processing. The metrics.log file is a sampling of the top ten items in each category in 30 second intervals, based on the size of _raw. It can be used for limited analysis of volume trends for data inputs. For more information about metrics.log, see About metrics.log and Work with metrics.log in this manual.|
|migration.log||A log of events during install and migration. Specifies which files were altered during upgrade.|
|python.log||Python events within Splunk. Useful for debugging REST endpoints, communication with splunkd, PDF Report Server App, Splunk Web display issues, sendmail (email alerts), and scripted inputs. With web_service.log, one of the few Splunk logs that uses "WARNING" instead of "WARN" for second most verbose logging level.|
|remote_searches.log||Messages from StreamedSearch channel. This code is executed on the search peers when a search head makes a search request. So this file contains useful information on indexers regarding searches they're participating in.|
|scheduler.log||All actions (successful or unsuccessful) performed by the splunkd search and alert scheduler. Typically, this shows scheduled search activity.|
|searches.log|| Beginning with Splunk 5, no longer used. Instead, use the following search syntax: |
|searchhistory.log||No longer used.|
|splunkd.log|| The primary log written to by the Splunk server. May be requested by Splunk Support for troubleshooting purposes. Any |
|splunkd_access.log||Any action done from splunkd through the UI is logged here, including splunkweb, the CLI, all POST GET actions, deleted saved searches, and other programs accessing the REST endpoints. Also logs the time taken to respond to the requests. Search job artifacts logged here include size of data returned with search. sourcetype="splunkd_access"|
|splunkd_stderr.log||The Unix standard error device for the server. Typically this contains (for *nix) times of healthy start and stop events, as well as various errors like exceptions, assertions, and errors generated by libraries and the operating system.|
|splunkd_stdout.log||The Unix standard output device for the server.|
|splunkd-utility.log|| This log is written to by the prereq-checking utils |
|web_access.log||Requests made of Splunk Web, in an Apache access_log format.|
|web_service.log||Primary log written by splunkweb. Records actions made by splunkweb. This and python.log are the only logs that, in second most verbose logging level, write messages with "WARNING" instead of Splunk log files' usual "WARN."|
Splunk Enterprise platform instrumentation refers to data that your Splunk Enterprise deployment logs in the _introspection index. It gathers data about your Splunk instance and operating system and writes it to log files that you can search later to aid in troubleshooting a variety of problems. You can also view the data at REST endpoints.
Read more in "About Splunk Enterprise platform instrumentation" in this manual.
Splunk search logs
Splunk also creates search logs. Note that these are not indexed to _internal.
Each search has its own directory for all information specific to the search, including its search logs. The search's directory is named with (among other parameters) the search_id. (Match a search to its search_id in audit.log.) You'll find the search directory in
If you have any long-running real-time searches, you might want to adjust the maximum size of your search logs. These logs are rotated when they reach a default maximum size of 25 MB. Splunk keeps up to five of them for each search, so the total log size for a search can conceivably grow as large as 125 MB.
Most searches are unlikely to generate logs anywhere near 25 MB in size; however, it can become an issue if you have ongoing real-time searches.
To adjust the log size, edit
Splunk has a debugging parameter. Read about enabling debug logging in this manual.
Except where noted above, Splunk's internal logging levels are
DEBUG INFO WARN ERROR FATAL (from most to least verbose).
Note: Running Splunk with debugging turned on outputs a large amount of information. Make sure you do not leave debugging on for any significant length of time.
Use Splunk Web to manage logs
To view and manage logs, you can use Splunk Web:
1. Navigate to Settings > System settings > System logging. This generates a list of log channels and their status.
2. To change the logging level for a particular log channel, click on that channel. This brings up a page specific to that channel.
3. On the log channel's page, you can change its logging level.
When you change the logging level, note the following:
- The change is immediate and dynamic.
- The change is not persistent; it goes away when Splunk is restarted.
Settings > System settings > System logging is meant only for dynamic and temporary changes to Splunk log files. For permanent changes, use
Included data models
Splunk comes with two sample data models. These data models are constructed from Splunk's internal logs. By interacting with them, you can learn about Splunk's log files and about data models in one fell swoop.
To access the internal log data models, click Pivot. By default, you should see two data models, "Splunk's Internal Audit Logs - SAMPLE" and "Splunk's Internal Server Logs - SAMPLE."
Note that there is a known issue in the alerts section of the "Splunk's Internal Server Logs" data model.