topic Re: Indexes.conf in Deployment Architecture

Indexes.conf

shawno — Wed, 14 Feb 2018 23:35:22 GMT

I'm trying to source what indexes.conf is being utilized for each index; for example, I have an index called Web. What I'd like to configure is the total max size of 275GB for that index using a retirement and archiving policy (maxTotalDataSizeMB). But I don't know what index applies to what Indexes.conf (several are listed). Further, can I set up a different index to use as indexes.conf (not the default)?

Re: Indexes.conf

MuS — Wed, 14 Feb 2018 23:45:07 GMT

Hi shawno,

you can use the following Splunk CLI command:

 $SPLUNK_HOME/bin/splunk btool indexes list --debug

This will show you the config file path so you will know where to change the settings.

And yes, you should use your own file in either $SPLUNK_HOME/etc/system/local or $SPLUNK_HOME/etc/apps/<yourappnamehere>/local.

Never change any setting in any file in $SPLUNK_HOME/etc/system/default.

Hope this helps ...

cheers, MuS

Re: Indexes.conf

shawno — Wed, 14 Feb 2018 23:59:02 GMT

That didn't work!

./btool web list --debug
/opt/splunk/bin/splunkd: error while loading shared libraries: libjemalloc.so.2: cannot open shared object file: No such file or directory

Re: Indexes.conf

shawno — Wed, 14 Feb 2018 23:59:46 GMT

./btool indexes list --debug

Re: Indexes.conf

MuS — Thu, 15 Feb 2018 00:06:13 GMT

you are not using the command I posted and most likely you are doing it not as the splunk user. Switch user to the Splunk user account (in most cases splunk) and run the correct command as posted 😉

Re: Indexes.conf

shawno — Thu, 15 Feb 2018 03:24:17 GMT

Sorry posted it wrong; I used ./btool indexes list --debug

Also used the username splunk with ./btool indexes list --debug

/opt/splunk/bin/splunkd: error while loading shared libraries: libjemalloc.so.2: cannot open shared object file: No such file or directory

Re: Indexes.conf

micahkemp — Thu, 15 Feb 2018 04:04:05 GMT

The command listed was ./splunk btool, not btool.

The btool command, despite having a binary right next to the splunk binary, has to be called from splunk, not directly.