<?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 Wrap a webhook for use with HTTP Event Collector in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Wrap-a-webhook-for-use-with-HTTP-Event-Collector/m-p/241697#M46860</link>
    <description>&lt;P&gt;I have an external system that generates a Webhook that can be posted to a URL of my choosing.  I would like to log this event as is with a sourcetype of my choosing to an index of my choosing.  I looked at the Splunk HTTP Event Collector, but it requires the event to be&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;{
  "event": { "webhook": "data" }
}
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;as well as having the Authorization header added onto it.&lt;/P&gt;

&lt;P&gt;How can I do this?&lt;/P&gt;</description>
    <pubDate>Fri, 22 Jan 2016 14:45:19 GMT</pubDate>
    <dc:creator>joxley</dc:creator>
    <dc:date>2016-01-22T14:45:19Z</dc:date>
    <item>
      <title>Wrap a webhook for use with HTTP Event Collector</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Wrap-a-webhook-for-use-with-HTTP-Event-Collector/m-p/241697#M46860</link>
      <description>&lt;P&gt;I have an external system that generates a Webhook that can be posted to a URL of my choosing.  I would like to log this event as is with a sourcetype of my choosing to an index of my choosing.  I looked at the Splunk HTTP Event Collector, but it requires the event to be&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;{
  "event": { "webhook": "data" }
}
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;as well as having the Authorization header added onto it.&lt;/P&gt;

&lt;P&gt;How can I do this?&lt;/P&gt;</description>
      <pubDate>Fri, 22 Jan 2016 14:45:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Wrap-a-webhook-for-use-with-HTTP-Event-Collector/m-p/241697#M46860</guid>
      <dc:creator>joxley</dc:creator>
      <dc:date>2016-01-22T14:45:19Z</dc:date>
    </item>
    <item>
      <title>Re: Wrap a webhook for use with HTTP Event Collector</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Wrap-a-webhook-for-use-with-HTTP-Event-Collector/m-p/241698#M46861</link>
      <description>&lt;P&gt;The solution I used was to run Nginx in front of the universal forwarder to wrap the event data and add the header:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;location /webhook-GUID {
    proxy_pass            &lt;A href="https://localhost:8088/services/collector" target="test_blank"&gt;https://localhost:8088/services/collector&lt;/A&gt;;
    proxy_read_timeout    90;
    proxy_connect_timeout 90;
    proxy_redirect        off;
    proxy_set_header      Host $host;
    proxy_set_header      X-Real-IP $remote_addr;
    proxy_set_header      X-Forwarded-For $proxy_add_x_forwarded_for;

    # wrap the webhook body for splunk
    proxy_set_body        "{\"event\":$request_body}";
    # Add the Splunk token into the Authorization header
    proxy_set_header      Authorization "Splunk HTTP-EC-TOKEN";
}
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;STRONG&gt;&lt;A href="https://oxo42.github.io/splunk/2016/01/21/splunk-wrap-a-webhook-for-delivery-to-an-http-event-collector/"&gt;Wrap a webhook for delivery to an HTTP event collector&lt;/A&gt;&lt;/STRONG&gt; is my blog post about getting webhook data from FogBugz into Splunk.&lt;/P&gt;</description>
      <pubDate>Fri, 22 Jan 2016 14:45:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Wrap-a-webhook-for-use-with-HTTP-Event-Collector/m-p/241698#M46861</guid>
      <dc:creator>joxley</dc:creator>
      <dc:date>2016-01-22T14:45:42Z</dc:date>
    </item>
    <item>
      <title>Re: Wrap a webhook for use with HTTP Event Collector</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Wrap-a-webhook-for-use-with-HTTP-Event-Collector/m-p/241699#M46862</link>
      <description>&lt;P&gt;@joxley if you are using Splunk Cloud you can use our new &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.3.1511/RESTREF/RESTinput#services.2Fcollector.2Fraw"&gt;/services/collector/raw&lt;/A&gt; endpoint which allows sending arbitrary data formats. This will also be available soon in Splunk Enterprise.&lt;/P&gt;

&lt;P&gt;If you are not in cloud today, then doing something like you did with nginx is a reasonable work around.&lt;/P&gt;</description>
      <pubDate>Sun, 14 Feb 2016 04:57:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Wrap-a-webhook-for-use-with-HTTP-Event-Collector/m-p/241699#M46862</guid>
      <dc:creator>gblock_splunk</dc:creator>
      <dc:date>2016-02-14T04:57:10Z</dc:date>
    </item>
    <item>
      <title>Re: Wrap a webhook for use with HTTP Event Collector</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Wrap-a-webhook-for-use-with-HTTP-Event-Collector/m-p/241700#M46863</link>
      <description>&lt;P&gt;You can also add HTTP webhooks really simply using HTTP Forwarder:&lt;/P&gt;

&lt;P&gt;&lt;A href="https://www.httpforwarder.com/"&gt;https://www.httpforwarder.com/&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;It will automatically reformat the event to fit Splunk's _JSON sourcetype and append correct Splunk headers.&lt;/P&gt;</description>
      <pubDate>Fri, 09 Sep 2016 20:26:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Wrap-a-webhook-for-use-with-HTTP-Event-Collector/m-p/241700#M46863</guid>
      <dc:creator>himynamesdave</dc:creator>
      <dc:date>2016-09-09T20:26:47Z</dc:date>
    </item>
    <item>
      <title>Re: Wrap a webhook for use with HTTP Event Collector</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Wrap-a-webhook-for-use-with-HTTP-Event-Collector/m-p/241701#M46864</link>
      <description>&lt;P&gt;@joxley today this using something like nginx is the right way to do it, but a better way is coming shortly, stay tuned. Also another option is to use this node &lt;A href="https://github.com/rarsan/splunk-hec-proxy"&gt;app&lt;/A&gt; which gives your a proxy.  In terms of the payload, our newer &lt;A href="http://dev.splunk.com/view/event-collector/SP-CAAAE8Y#raw"&gt;raw&lt;/A&gt; endpoint is perfect for receiving the standard webhook payload. As you observed the auth header is still required &lt;EM&gt;today&lt;/EM&gt;, but that will change.&lt;/P&gt;</description>
      <pubDate>Sat, 10 Sep 2016 05:38:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Wrap-a-webhook-for-use-with-HTTP-Event-Collector/m-p/241701#M46864</guid>
      <dc:creator>gblock_splunk</dc:creator>
      <dc:date>2016-09-10T05:38:58Z</dc:date>
    </item>
    <item>
      <title>Re: Wrap a webhook for use with HTTP Event Collector</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Wrap-a-webhook-for-use-with-HTTP-Event-Collector/m-p/241702#M46865</link>
      <description>&lt;P&gt;when i click on the link you gave, it says page doesn't exist. ;(&lt;/P&gt;</description>
      <pubDate>Tue, 27 Sep 2016 18:29:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Wrap-a-webhook-for-use-with-HTTP-Event-Collector/m-p/241702#M46865</guid>
      <dc:creator>japala</dc:creator>
      <dc:date>2016-09-27T18:29:31Z</dc:date>
    </item>
    <item>
      <title>Re: Wrap a webhook for use with HTTP Event Collector</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Wrap-a-webhook-for-use-with-HTTP-Event-Collector/m-p/241703#M46866</link>
      <description>&lt;P&gt;page does not exist!&lt;/P&gt;</description>
      <pubDate>Wed, 16 May 2018 23:15:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Wrap-a-webhook-for-use-with-HTTP-Event-Collector/m-p/241703#M46866</guid>
      <dc:creator>jtlittle</dc:creator>
      <dc:date>2018-05-16T23:15:57Z</dc:date>
    </item>
  </channel>
</rss>

