Is there a way to run cmd btool check via rest?

[ddrillic]

@harsmarvania57 suggested to use the lovely and useful ./splunk cmd btool check command In When modifying serverclass which safeguards could help us avoid the following mistakes?

Since most of our users use Jenkins to deploy their code, is there a way to run this command via rest?

[gabriel_vasseur]

I don't think https://splunkbase.splunk.com/app/1607/ has any chance of being installed in splunk cloud.

Someone at splunk suggested we try https://splunkbase.splunk.com/app/6368/ which we had no trouble getting installed in cloud and it's working for us.

[MuS · Accepted solution]

Hi ddrillic,

there might be something, because the old S.O.S app used it by using a custom command.

But why not use the https://splunkbase.splunk.com/app/1607/ that will provide shell access within Splunk where one can run btool for example.

Hope this helps ...

cheers, MuS

[ddrillic]

@MuS, is there a way to restrict this app, to run only the btool command? with the Unix sudo command for example, we can restrict which commands can run...

[MuS]

Which one are you referring @ddrillic ? If it is this one https://splunkbase.splunk.com/app/1607/ then it is just a python script which can be modified so it only runs btool for example.

cheers, MuS

[ddrillic]

Very interesting @MuS.

[ddrillic]

Much appreciated @MuS

[MuS]

Okay, S.O.S app had a custom command called btool in it https://answers.splunk.com/answers/104622/make-output-of-btool-some-conf-type-list-more-legible-unix... You can still download the app here https://splunkbase.splunk.com/app/748/#/overview Not sure though if you can use it to do btool check but well worth to give it a try 😉

cheers, MuS

[gjanders]

Or refer to Btool Scripted Inputs for Splunk if you go down this particular path...

[ddrillic]

Thank you @gjanders

[wrangler2x]

One thing you can't do with it is pipe to something else. This would normally show all the inputs.conf stanza names but in the app it just shows you usage info. Here on *nix:

$ splunk cmd btool inputs list --debug | grep "\["

/opt/splunk/etc/apps/unix/local/inputs.conf                            [script:///opt/splunk/etc/apps/unix/bin/ps.sh]
/opt/splunk/etc/apps/unix/local/inputs.conf                            [script:///opt/splunk/etc/apps/unix/bin/rlog.sh]
/opt/splunk/etc/apps/unix/local/inputs.conf                            [script:///opt/splunk/etc/apps/unix/bin/time.sh]
/opt/splunk/etc/apps/unix/local/inputs.conf                            [script:///opt/splunk/etc/apps/unix/bin/top.sh]

etc...