<?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 Universal Forwarder .... as a language API in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-as-a-language-API/m-p/33819#M6069</link>
    <description>&lt;P&gt;Are there any plans to release a UF programming API ? Not the full blown UF functionality, but maybe just the output logic/protocol to start with.&lt;BR /&gt;
Then you could embed the UF API in deployed code, maybe as a reusable logging appender/handler for various language logging frameworks(log4j, logback, python logging module etc..), encapsulate best practice Splunk logging semantics and the Splunk CIM(vs trusting developers to follow prescribed Splunk logging standards) and not have to go through the additional step of deploying a standalone Universal Forwarder where you control the engineered code.&lt;/P&gt;</description>
    <pubDate>Tue, 13 Dec 2011 09:37:29 GMT</pubDate>
    <dc:creator>Damien_Dallimor</dc:creator>
    <dc:date>2011-12-13T09:37:29Z</dc:date>
    <item>
      <title>Universal Forwarder .... as a language API</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-as-a-language-API/m-p/33819#M6069</link>
      <description>&lt;P&gt;Are there any plans to release a UF programming API ? Not the full blown UF functionality, but maybe just the output logic/protocol to start with.&lt;BR /&gt;
Then you could embed the UF API in deployed code, maybe as a reusable logging appender/handler for various language logging frameworks(log4j, logback, python logging module etc..), encapsulate best practice Splunk logging semantics and the Splunk CIM(vs trusting developers to follow prescribed Splunk logging standards) and not have to go through the additional step of deploying a standalone Universal Forwarder where you control the engineered code.&lt;/P&gt;</description>
      <pubDate>Tue, 13 Dec 2011 09:37:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-as-a-language-API/m-p/33819#M6069</guid>
      <dc:creator>Damien_Dallimor</dc:creator>
      <dc:date>2011-12-13T09:37:29Z</dc:date>
    </item>
    <item>
      <title>Re: Universal Forwarder .... as a language API</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-as-a-language-API/m-p/33820#M6070</link>
      <description>&lt;P&gt;Hi - We expect that the Splunk SDKs will be able to support this as they stand now in Preview release.  &lt;/P&gt;

&lt;P&gt;Python: &lt;A href="https://github.com/splunk/splunk-sdk-python"&gt;https://github.com/splunk/splunk-sdk-python&lt;/A&gt;&lt;BR /&gt;
Java (Available 12/15): &lt;A href="https://github.com/splunk/splunk-sdk-java"&gt;https://github.com/splunk/splunk-sdk-java&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Prior to a beta release of the SDKs we will be investigating and validating this.  Would enjoy hearing any feedback that you might have if you have already tried this.  &lt;A href="mailto:devinfo@splunk.com"&gt;devinfo@splunk.com&lt;/A&gt;  &lt;/P&gt;</description>
      <pubDate>Wed, 14 Dec 2011 00:59:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-as-a-language-API/m-p/33820#M6070</guid>
      <dc:creator>psanford_splunk</dc:creator>
      <dc:date>2011-12-14T00:59:37Z</dc:date>
    </item>
  </channel>
</rss>

