You can't put a schedule for when forwarding occurs, other than keeping the forwarder turned off and just turn it on when you need it. Have a look at these other questions that cover pretty much the same thing: http://splunk-base.splunk.com/answers/59916/can-you-set-a-certain-time-forwarding-occurs http://splunk-base.splunk.com/answers/58980/how-to-schedule-a-transfer-on-a-forwarder ... View more

You can see partially the solution you are looking for clicking on the following link: http://coverall.splunk.com/web_assets/education/splunk101/43/ReportsDashboards/index.htm ... View more

Like this: <form> <label>Using half of timepicker</label> <description>Using half of timepicker</description> <fieldset autoRun="true" submitButton="false"> <input type="time" token="time_tok1" searchWhenChanged="true"> <label>Chart Timespan/Width</label> <default>Last 24 hours</default> </input> </fieldset> <row> <chart> <title>Using earliest only</title> <searchString>earliest=$time_tok1.earliest$ latest=now() Your Search Here</searchString> </chart> </row> <row> <chart> <title>Using latest only</title> <searchString>earliest=0 latest=$time_tok1.latest$ Your Search Here</searchString> </chart> </row> </form> ... View more

Sorry I do not understand. Hope someone else can help you. ... View more

You should set inputs.conf with index=<indexname> so that the data coming from this input will end up destined for the specified index. If the data is ending up in two different places, perhaps the data is older and from a point where you hadn't defined the index where you wanted to see the data? If that is the case, you can't selectively move data from one index to another, so your data will remain in the original index. If you set up this input and you see current data ending up in two indexes, you've probably got a transform to route the data into another index someplace in your configuration. You can look at your btool output to determine if any of these things is occurring. Run the following command from $SPLUNK_HOME/bin/ on the indexer if you're using a UF/LWF, or on the heavy forwarder, if that is what your using. 'splunk cmd btool inputs list --debug > ~/inputs.out' 'splunk cmd btool props list --debug > ~/props.out' 'splunk cmd btool transforms list --debug > ~/transforms.out' ... View more

The login page live here: $SPLUNK_HOME/share/splunk/search_mrsparkle/templates/account/login.html you can edit whatever you want, but keep in mind that changes will be overwritten upon upgrade. ... View more

You are not necessarily limited by the number of forwarders per indexer, but rather by the amount of data your indexer can ingest. If your server for example is capable of indexing at ~70 MB/minute, and your indexers send 0.5 MB/minute, you can expect roughly 140 forwarders per indexer. It is however likely that your forwarders will send less data than that so the number of forwarders will likely be greater. In the end it really comes down to the hardware of your indexer. I recommend taking a look at Hardware capacity planning for your Splunk deployment in the docs and estimating the amount of data you want to index to get an idea of how many indexers you will need to support your forwarders. ... View more

Thanks ，vbumgarner！ ... View more