Welcome to Splunk Answers, a Q&A forum for users to find answers to questions about deploying, managing, and using Splunk products. Contributors of all backgrounds and levels of expertise come here to find solutions to their issues, and to help other users in the Splunk community with their own questions.

This quick tutorial will help you get started with key features to help you find the answers you need. You will receive 10 karma points upon successful completion!

People who like this

2 Answers

There aren't any. You should configure this either via editing configuration files (or having the files pushed out from Deployment Server or similar.)

I recommend always using configuration files for Splunk in preference to the CLI. Besides the fact that many options are unavailable via CLI, you can also define the desired configuration more precisely regardless of the initial state of the system. Most deployment management systems (including Splunk Deployment Server) work much better with configuration files than running commands, as file copying is idempotent.

I only use CLI for start, stop, setting user passwords (sometimes), and setting boot-start (sometimes), and one-time testing using the "oneshot" input.

Use these flags to specify whether or not Splunk should index a particular Windows event log.

* WINEVENTLOGAPPCHECK=1/0, off by default
* WINEVENTLOGSECCHECK=1/0, off by default
* WINEVENTLOGSYSCHECK=1/0, off by default
* WINEVENTLOGFWDCHECK=1/0, off by default
* WINEVENTLOGSETCHECK=1/0, off by default