<?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: What is the feasibility of using Splunk REST calls from an Angular application running HTLM5 to send data into Splunk directly from the browser? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/What-is-the-feasibility-of-using-Splunk-REST-calls-from-an/m-p/310298#M58310</link>
    <description>&lt;P&gt;This is an interesting use case.  This does &lt;STRONG&gt;certainly&lt;/STRONG&gt; look like an ideal use case for the http event collector on the heavy forwarder, here are a few reasons why:&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;The heavy forwarder with http event collector is built for this sort of demand&lt;/LI&gt;
&lt;LI&gt;Lightweight is relative, a solution needs to be available and resilient and scalable. &lt;/LI&gt;
&lt;LI&gt;Depending on how your network topology is segmented, you'll want a heavy forwarder with an http event collector  (not an indexer) as close to the edge as possible:  &lt;A href="http://dev.splunk.com/view/event-collector/SP-CAAAE73"&gt;http://dev.splunk.com/view/event-collector/SP-CAAAE73&lt;/A&gt; . see Scenario 2 &amp;amp; 3.  You didn't mention if this was for internet facing http calls, but I'm assuming they are. &lt;/LI&gt;
&lt;LI&gt;Reusability, should similar use cases arise in the future, you now have a solution that can be shared with other application needs. &lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;Cheers&lt;/P&gt;</description>
    <pubDate>Fri, 01 Dec 2017 18:12:54 GMT</pubDate>
    <dc:creator>murbanek_splunk</dc:creator>
    <dc:date>2017-12-01T18:12:54Z</dc:date>
    <item>
      <title>What is the feasibility of using Splunk REST calls from an Angular application running HTLM5 to send data into Splunk directly from the browser?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-is-the-feasibility-of-using-Splunk-REST-calls-from-an/m-p/310297#M58309</link>
      <description>&lt;P&gt;We have a partner who wants an extremely light interface to send data into a Splunk instance.&lt;BR /&gt;
They prefer to make a simple REST call directly from the browser to load a JSON payload into Splunk.&lt;BR /&gt;
The goal is to NOT have a heavy server-side process, but rather a lightweight REST interface directly to Splunk.&lt;/P&gt;

&lt;P&gt;The data would be keyed on the user working in the browser at the time of the call out. &lt;BR /&gt;
The data would be accessed in a Splunk dashboard/report keying on the user and his/her data.&lt;/P&gt;

&lt;P&gt;I saw a recommendation from another post regarding HTTP Event Collector for this purpose.  On first thought this seems feasible, but I am interested in knowing the pluses and minuses of both solutions.&lt;/P&gt;

&lt;P&gt;Regards.&lt;/P&gt;</description>
      <pubDate>Fri, 01 Dec 2017 17:36:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-is-the-feasibility-of-using-Splunk-REST-calls-from-an/m-p/310297#M58309</guid>
      <dc:creator>jamesoconnell</dc:creator>
      <dc:date>2017-12-01T17:36:01Z</dc:date>
    </item>
    <item>
      <title>Re: What is the feasibility of using Splunk REST calls from an Angular application running HTLM5 to send data into Splunk directly from the browser?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-is-the-feasibility-of-using-Splunk-REST-calls-from-an/m-p/310298#M58310</link>
      <description>&lt;P&gt;This is an interesting use case.  This does &lt;STRONG&gt;certainly&lt;/STRONG&gt; look like an ideal use case for the http event collector on the heavy forwarder, here are a few reasons why:&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;The heavy forwarder with http event collector is built for this sort of demand&lt;/LI&gt;
&lt;LI&gt;Lightweight is relative, a solution needs to be available and resilient and scalable. &lt;/LI&gt;
&lt;LI&gt;Depending on how your network topology is segmented, you'll want a heavy forwarder with an http event collector  (not an indexer) as close to the edge as possible:  &lt;A href="http://dev.splunk.com/view/event-collector/SP-CAAAE73"&gt;http://dev.splunk.com/view/event-collector/SP-CAAAE73&lt;/A&gt; . see Scenario 2 &amp;amp; 3.  You didn't mention if this was for internet facing http calls, but I'm assuming they are. &lt;/LI&gt;
&lt;LI&gt;Reusability, should similar use cases arise in the future, you now have a solution that can be shared with other application needs. &lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;Cheers&lt;/P&gt;</description>
      <pubDate>Fri, 01 Dec 2017 18:12:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-is-the-feasibility-of-using-Splunk-REST-calls-from-an/m-p/310298#M58310</guid>
      <dc:creator>murbanek_splunk</dc:creator>
      <dc:date>2017-12-01T18:12:54Z</dc:date>
    </item>
    <item>
      <title>Re: What is the feasibility of using Splunk REST calls from an Angular application running HTLM5 to send data into Splunk directly from the browser?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-is-the-feasibility-of-using-Splunk-REST-calls-from-an/m-p/310299#M58311</link>
      <description>&lt;P&gt;Thanks for the quick response Michael.&lt;BR /&gt;&lt;BR /&gt;
I'll work with our partner to get them started on using our existing HTTP Event Collectors.&lt;BR /&gt;
cheers, &lt;BR /&gt;
-Jim O.&lt;/P&gt;</description>
      <pubDate>Fri, 01 Dec 2017 18:29:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-is-the-feasibility-of-using-Splunk-REST-calls-from-an/m-p/310299#M58311</guid>
      <dc:creator>jamesoconnell</dc:creator>
      <dc:date>2017-12-01T18:29:57Z</dc:date>
    </item>
  </channel>
</rss>

