<?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: TCP Input to Splunk lnput from SAAS App in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/TCP-Input-to-Splunk-lnput-from-SAAS-App/m-p/378830#M68507</link>
    <description>&lt;P&gt;Hi, Thanks for that info, I will have to setup the java project with the custom HEC appender.&lt;/P&gt;

&lt;P&gt;I had looked into that, but the tcp input setup is so much simpler.&lt;/P&gt;</description>
    <pubDate>Tue, 12 Feb 2019 02:11:23 GMT</pubDate>
    <dc:creator>stevescottmb</dc:creator>
    <dc:date>2019-02-12T02:11:23Z</dc:date>
    <item>
      <title>TCP Input to Splunk lnput from SAAS App</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/TCP-Input-to-Splunk-lnput-from-SAAS-App/m-p/378828#M68505</link>
      <description>&lt;P&gt;I have a java application running in an AWS instance. I want to use the following log4j2 appender to push logs directly into the TCP input in Splunk Cloud;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;&amp;lt;Appenders&amp;gt;
    &amp;lt;Socket name="socket" host="{cloudsplunk.host}" port="{cloudsplunk.host}"&amp;gt;
    &amp;lt;PatternLayout pattern="%p: %m%n" charset="UTF-8"/&amp;gt;
    &amp;lt;/Socket&amp;gt;
&amp;lt;/Appenders&amp;gt;
&amp;lt;Loggers&amp;gt;
    &amp;lt;Root level="INFO"&amp;gt;
    &amp;lt;/Root&amp;gt;
    &amp;lt;Logger name="splunk.logger" level="info"&amp;gt;
    &amp;lt;AppenderRef ref="socket"/&amp;gt;
    &amp;lt;/Logger&amp;gt;
&amp;lt;/Loggers&amp;gt;
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;However, it seems I have to create a universal forwarder, but I cannot install a forwarder on that EC2 instance ? &lt;/P&gt;

&lt;P&gt;I just want to push the log4j2 output directly into the Splunk TCP Input, is this possible on Splunk Cloud? We are currently on a trial instance, so maybe I cannot see this option until we move to Enterprise.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Feb 2019 19:41:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/TCP-Input-to-Splunk-lnput-from-SAAS-App/m-p/378828#M68505</guid>
      <dc:creator>stevescottmb</dc:creator>
      <dc:date>2019-02-11T19:41:43Z</dc:date>
    </item>
    <item>
      <title>Re: TCP Input to Splunk lnput from SAAS App</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/TCP-Input-to-Splunk-lnput-from-SAAS-App/m-p/378829#M68506</link>
      <description>&lt;P&gt;This can be done many ways, but the simplest and easiest is by using the &lt;CODE&gt;Http Event Collector&lt;/CODE&gt;:&lt;/P&gt;

&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Data/UsetheHTTPEventCollector"&gt;https://docs.splunk.com/Documentation/Splunk/latest/Data/UsetheHTTPEventCollector&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Feb 2019 02:04:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/TCP-Input-to-Splunk-lnput-from-SAAS-App/m-p/378829#M68506</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2019-02-12T02:04:47Z</dc:date>
    </item>
    <item>
      <title>Re: TCP Input to Splunk lnput from SAAS App</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/TCP-Input-to-Splunk-lnput-from-SAAS-App/m-p/378830#M68507</link>
      <description>&lt;P&gt;Hi, Thanks for that info, I will have to setup the java project with the custom HEC appender.&lt;/P&gt;

&lt;P&gt;I had looked into that, but the tcp input setup is so much simpler.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Feb 2019 02:11:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/TCP-Input-to-Splunk-lnput-from-SAAS-App/m-p/378830#M68507</guid>
      <dc:creator>stevescottmb</dc:creator>
      <dc:date>2019-02-12T02:11:23Z</dc:date>
    </item>
  </channel>
</rss>

