<?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: Splunk not receiving any events from custom (scripted) inputs in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-not-receiving-any-events-from-custom-scripted-inputs/m-p/16229#M1913</link>
    <description>&lt;P&gt;Yes, your scripted input should write event out to the console aka 
"stdout" (standard output).  (Normally this is accomplised using a "print" or "echo" command, depending on your programming environment).  Anything written to "stderr" (standard error) will also be stored in the &lt;CODE&gt;_internal&lt;/CODE&gt; index because it's assumed to be an error message.&lt;/P&gt;

&lt;P&gt;Finding your events within splunk will depend on your settings in your &lt;CODE&gt;inputs.conf&lt;/CODE&gt; entry for your scripted input.  Specifically the "index", "host", "source" and "sourcetype" settings will dictate where and how your events are stored by splunk.  (You can always just search for a unique term that you know your scripted input will be writing out.)  But I would recommend explicitly setting a source and sourcetype for your scripted input.&lt;/P&gt;

&lt;P&gt;I would also suggest that you look in the internal index for any errors.  Try the following search:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; index=_internal sourcetype=splunkd ExecProcessor
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This should give you a starting point as to what errors (if any) have being encountered.&lt;/P&gt;</description>
    <pubDate>Sat, 26 Jun 2010 03:50:20 GMT</pubDate>
    <dc:creator>Lowell</dc:creator>
    <dc:date>2010-06-26T03:50:20Z</dc:date>
    <item>
      <title>Splunk not receiving any events from custom (scripted) inputs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-not-receiving-any-events-from-custom-scripted-inputs/m-p/16228#M1912</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;I created a windows executable which reads lines from a file and outputs to console and made Splunk run this - but I had no luck finding the results in my search. I am currently running a .bat file in my inputs.conf (which runs the .exe). I can see my script was added to the list of scripts but it does not seem to be working. &lt;/P&gt;

&lt;P&gt;I am curious if writing to console is the right way to pass the data into Splunk. If it is where could I be wrong? Any help would be greatly appreciated!&lt;/P&gt;</description>
      <pubDate>Sat, 26 Jun 2010 03:14:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-not-receiving-any-events-from-custom-scripted-inputs/m-p/16228#M1912</guid>
      <dc:creator>hiwell</dc:creator>
      <dc:date>2010-06-26T03:14:31Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk not receiving any events from custom (scripted) inputs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-not-receiving-any-events-from-custom-scripted-inputs/m-p/16229#M1913</link>
      <description>&lt;P&gt;Yes, your scripted input should write event out to the console aka 
"stdout" (standard output).  (Normally this is accomplised using a "print" or "echo" command, depending on your programming environment).  Anything written to "stderr" (standard error) will also be stored in the &lt;CODE&gt;_internal&lt;/CODE&gt; index because it's assumed to be an error message.&lt;/P&gt;

&lt;P&gt;Finding your events within splunk will depend on your settings in your &lt;CODE&gt;inputs.conf&lt;/CODE&gt; entry for your scripted input.  Specifically the "index", "host", "source" and "sourcetype" settings will dictate where and how your events are stored by splunk.  (You can always just search for a unique term that you know your scripted input will be writing out.)  But I would recommend explicitly setting a source and sourcetype for your scripted input.&lt;/P&gt;

&lt;P&gt;I would also suggest that you look in the internal index for any errors.  Try the following search:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; index=_internal sourcetype=splunkd ExecProcessor
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This should give you a starting point as to what errors (if any) have being encountered.&lt;/P&gt;</description>
      <pubDate>Sat, 26 Jun 2010 03:50:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-not-receiving-any-events-from-custom-scripted-inputs/m-p/16229#M1913</guid>
      <dc:creator>Lowell</dc:creator>
      <dc:date>2010-06-26T03:50:20Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk not receiving any events from custom (scripted) inputs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-not-receiving-any-events-from-custom-scripted-inputs/m-p/16230#M1914</link>
      <description>&lt;P&gt;Thanks for your reply! I actually got it going now. I have another question though, is it possible to edit sourcetype and all through the inputs.conf or props.conf even though you added the script through Manager -&amp;gt; Data Inputs -&amp;gt; Scripts? The splunk documentation (&lt;A href="http://www.splunk.com/base/Documentation/4.1.3/Admin/Setupcustom(scripted)inputs"&gt;http://www.splunk.com/base/Documentation/4.1.3/Admin/Setupcustom(scripted)inputs&lt;/A&gt;) shows you two ways to do it and my impression was that you have to work one way or the other and not get the mixed up.&lt;/P&gt;</description>
      <pubDate>Sat, 26 Jun 2010 04:15:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-not-receiving-any-events-from-custom-scripted-inputs/m-p/16230#M1914</guid>
      <dc:creator>hiwell</dc:creator>
      <dc:date>2010-06-26T04:15:38Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk not receiving any events from custom (scripted) inputs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-not-receiving-any-events-from-custom-scripted-inputs/m-p/16231#M1915</link>
      <description>&lt;P&gt;Pretty much everything that you do configure from the UI simply generates a config file entry.  So you should be able to find your scripted input in one of the &lt;CODE&gt;inputs.conf&lt;/CODE&gt; files on your system.  (Check various &lt;CODE&gt;local&lt;/CODE&gt; directories.)  There is also something in the docs called "How config files work" (or something like that) I would recommend that you read that if your new to splunk and it's config files.&lt;/P&gt;</description>
      <pubDate>Sat, 26 Jun 2010 04:41:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-not-receiving-any-events-from-custom-scripted-inputs/m-p/16231#M1915</guid>
      <dc:creator>Lowell</dc:creator>
      <dc:date>2010-06-26T04:41:24Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk not receiving any events from custom (scripted) inputs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-not-receiving-any-events-from-custom-scripted-inputs/m-p/16232#M1916</link>
      <description>&lt;P&gt;cool cool everything good to go now&lt;/P&gt;</description>
      <pubDate>Wed, 30 Jun 2010 01:20:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-not-receiving-any-events-from-custom-scripted-inputs/m-p/16232#M1916</guid>
      <dc:creator>hiwell</dc:creator>
      <dc:date>2010-06-30T01:20:33Z</dc:date>
    </item>
  </channel>
</rss>

