not that im aware of, you'll have to create a domain account. change the splunkd user to the domain account and then give the domain account access to that share.
... View more
yes you could technically put them in search it would be better if you created a separate app for them if not just for organization. What i meant by indexer though is a splunk instance whose role is an indexer. If you are running a standalone my point is mute. Can you tell me what your environment looks like and i can tailor my answer a little better?
... View more
run a subsearch using |join .
"search"
| join type=inner
[ |search "search" earliest=x latest=x]
Set the time picker as two weeks prior, the sub search would be the current time range. This should only show you events that were persistent between the two weeks
http://docs.splunk.com/Documentation/Splunk/7.1.2/SearchReference/Join
... View more
its best practice to not put anything in system/local you could even put it etc/apps/search if you so desired but more importantly just to make sure you put these on the indexer correct?
... View more
The default power role already inherits user. If you are looking to make a custom role based off power, inheriting from power should suffice.
... View more
use |append and run the search again as a subsearch with a hard coded time range using earliest=-15m latest=now and your time picker could be 24hrs or you can leave it in your search as well. whatever field you are using to calculate on will need to be different than your main search for instance |"search" |stats count(a) as ex1 |append[|search "search' earliest=-15m latest=now |stats count(a) as ex2] Keep in mind there is a default subsearch timeout of 60s.
... View more
never used it but it seems pretty straight forward. You just define what customers/groups use what indexes. Personally id just install it in my dev enviroment and just look at all the searches to get a better understanding, this is your best bet.
... View more
you can still use the monitor type input, it just wont show you a preview of the data before ingesting for remote hosts. This is working as intended.
... View more
try using join
then forcing the time range just like you have done above in your sub search. Be aware of subsearch timeouts though, I believe default is 60 seconds.
... View more
@skoelpin is referring to something like this
| appendpipe
[ |stats count(a) as a
| eval empty=if(isnum(a),"0", "a")]
you would have to add the append to for each category a, b, c... etc
... View more
I dont believe you can, i was in a similar situation and just had change permissions one by one. which realistically does take to long just tedious. Keep in mind not all apps in the drop down are visible in the first place by default so that should shrink your list a bit.
you could change
[ui]
is_visible = 0
in app.conf but this will hide the app from all users but still allow access to all the KO and app if you know the path.
... View more
according to the documentation yes, upgrade your forwarders to 6.5 first.
From version 6.5 or later to 7.1 on Splunk universal forwarders.
http://docs.splunk.com/Documentation/Splunk/7.1.1/Installation/AboutupgradingREADTHISFIRST
... View more