<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Setting up an ultra-light front-end instance for API request in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Setting-up-an-ultra-light-front-end-instance-for-API-request/m-p/119683#M24914</link>
    <description>&lt;P&gt;I will (almost) answer my own question after some searching.&lt;/P&gt;

&lt;P&gt;A (very brutal) way to do it is by using the CLI commands, namely&lt;BR /&gt;
 * Install Splunk locally and start its daemon&lt;BR /&gt;
 * Launch a query from the command line similar to &lt;EM&gt;splunk search 'earliest=-10m latest=-1m index=foo host="bar*" sourcetype="test" "some text" AND NOT "other" ' -uri &lt;A href="https://remote-splunk:port"&gt;https://remote-splunk:port&lt;/A&gt;&lt;/EM&gt;&lt;/P&gt;

&lt;P&gt;Downside is that the first time you are prompted for username/password of the remote host.&lt;/P&gt;

&lt;P&gt;Obviously this will only work well for local scripting or batch jobs, not used by a high request-volume server/process.&lt;/P&gt;

&lt;P&gt;I hope this helps.&lt;/P&gt;</description>
    <pubDate>Fri, 01 Nov 2013 17:07:18 GMT</pubDate>
    <dc:creator>sgerogia</dc:creator>
    <dc:date>2013-11-01T17:07:18Z</dc:date>
    <item>
      <title>Setting up an ultra-light front-end instance for API request</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Setting-up-an-ultra-light-front-end-instance-for-API-request/m-p/119682#M24913</link>
      <description>&lt;P&gt;Hello.&lt;/P&gt;

&lt;P&gt;In our company we already have a Splunk 5 setup with multiple search heads and indexers.&lt;/P&gt;

&lt;P&gt;What I would like to do is setup a local Splunk instance, which would just accept REST API requests, simply relay them to the existing search head(s) and return back results.&lt;BR /&gt;
As minimum data as possible are to be maintained on this light instance; I like to think of it as a query proxy.&lt;/P&gt;

&lt;P&gt;Does Splunk support this topology?&lt;/P&gt;

&lt;P&gt;If yes, which settings in the light instance should I look into? Or perhaps some page in the online docs that I have missed?&lt;/P&gt;

&lt;P&gt;Thank you,&lt;BR /&gt;
S.&lt;/P&gt;

&lt;P&gt;UPDATE:&lt;BR /&gt;
I forgot to clarify that, for whatever historical/obscure reason, direct REST API access to the search heads has been disabled.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Oct 2013 13:16:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Setting-up-an-ultra-light-front-end-instance-for-API-request/m-p/119682#M24913</guid>
      <dc:creator>sgerogia</dc:creator>
      <dc:date>2013-10-29T13:16:30Z</dc:date>
    </item>
    <item>
      <title>Re: Setting up an ultra-light front-end instance for API request</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Setting-up-an-ultra-light-front-end-instance-for-API-request/m-p/119683#M24914</link>
      <description>&lt;P&gt;I will (almost) answer my own question after some searching.&lt;/P&gt;

&lt;P&gt;A (very brutal) way to do it is by using the CLI commands, namely&lt;BR /&gt;
 * Install Splunk locally and start its daemon&lt;BR /&gt;
 * Launch a query from the command line similar to &lt;EM&gt;splunk search 'earliest=-10m latest=-1m index=foo host="bar*" sourcetype="test" "some text" AND NOT "other" ' -uri &lt;A href="https://remote-splunk:port"&gt;https://remote-splunk:port&lt;/A&gt;&lt;/EM&gt;&lt;/P&gt;

&lt;P&gt;Downside is that the first time you are prompted for username/password of the remote host.&lt;/P&gt;

&lt;P&gt;Obviously this will only work well for local scripting or batch jobs, not used by a high request-volume server/process.&lt;/P&gt;

&lt;P&gt;I hope this helps.&lt;/P&gt;</description>
      <pubDate>Fri, 01 Nov 2013 17:07:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Setting-up-an-ultra-light-front-end-instance-for-API-request/m-p/119683#M24914</guid>
      <dc:creator>sgerogia</dc:creator>
      <dc:date>2013-11-01T17:07:18Z</dc:date>
    </item>
    <item>
      <title>Re: Setting up an ultra-light front-end instance for API request</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Setting-up-an-ultra-light-front-end-instance-for-API-request/m-p/119684#M24915</link>
      <description>&lt;P&gt;You have read this?&lt;/P&gt;

&lt;P&gt;&lt;A href="http://dev.splunk.com/view/rest-api-overview/SP-CAAADP8"&gt;http://dev.splunk.com/view/rest-api-overview/SP-CAAADP8&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 01 Nov 2013 17:11:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Setting-up-an-ultra-light-front-end-instance-for-API-request/m-p/119684#M24915</guid>
      <dc:creator>dmaislin_splunk</dc:creator>
      <dc:date>2013-11-01T17:11:06Z</dc:date>
    </item>
    <item>
      <title>Re: Setting up an ultra-light front-end instance for API request</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Setting-up-an-ultra-light-front-end-instance-for-API-request/m-p/119685#M24916</link>
      <description>&lt;P&gt;This would obviously be better, I agree.&lt;BR /&gt;
Namely, make a REST call to the local Splunk which would relay it to the remote search head. Do you know how to set the equivalent of the -uri switch in the API request?&lt;/P&gt;</description>
      <pubDate>Fri, 01 Nov 2013 17:20:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Setting-up-an-ultra-light-front-end-instance-for-API-request/m-p/119685#M24916</guid>
      <dc:creator>sgerogia</dc:creator>
      <dc:date>2013-11-01T17:20:34Z</dc:date>
    </item>
  </channel>
</rss>

