<?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.Intersplunk.outputResults sending another header? Or bad commands.conf options? in Splunk Dev</title>
    <link>https://community.splunk.com/t5/Splunk-Dev/splunk-Intersplunk-outputResults-sending-another-header-Or-bad/m-p/78463#M1116</link>
    <description>&lt;P&gt;That output looks very strange.&lt;/P&gt;

&lt;P&gt;I'm unsure about all the settings for your command in command.conf.  &lt;/P&gt;

&lt;P&gt;I'm also unsure what your command is doing with the _time values -- whether it's casting them to a string, for example.&lt;/P&gt;

&lt;P&gt;This would be putting a bandaid on cancer, but you might want to look at the generates_timeorder and overrides_timeorder settings for your command in commands.conf.&lt;/P&gt;</description>
    <pubDate>Thu, 14 Apr 2011 11:04:53 GMT</pubDate>
    <dc:creator>carasso</dc:creator>
    <dc:date>2011-04-14T11:04:53Z</dc:date>
    <item>
      <title>splunk.Intersplunk.outputResults sending another header? Or bad commands.conf options?</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/splunk-Intersplunk-outputResults-sending-another-header-Or-bad/m-p/78462#M1115</link>
      <description>&lt;P&gt;When using splunk.Intersplunk.outputResults for even 1 record as a streaming command, I get an extra header with a improperly casted time field that ends up making the search compain about fields coming back in the wrong time order thus throwing an error.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;The external search command 'command' did not return events in descending time order, as expected.
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;if I turn off streaming, I get:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;    _time                    commandfield    logfield
1   4/3/74 10:46:24.314 AM   commandfield    logfield
2   4/8/11 10:00:26.000 PM   5.39677852134   value1
3   4/8/11 10:00:26.000 PM   5.39677852134   value2
4   4/8/11 10:00:12.000 PM   5.1593157535    value3
5   4/8/11 10:00:12.000 PM   5.1593157535    value4
6   4/8/11 9:59:55.000 PM    5.52337405618   value5
7   4/8/11 9:59:55.000 PM    5.53858132907   value6
8   4/8/11 9:59:55.000 PM    5.53426175508   value7
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I've tried using outputheader=true and I get zero results&lt;/P&gt;

&lt;P&gt;I'm probably doing something dumb, backwards or wrong but I just don't see it yet...&lt;/P&gt;</description>
      <pubDate>Sat, 09 Apr 2011 05:14:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/splunk-Intersplunk-outputResults-sending-another-header-Or-bad/m-p/78462#M1115</guid>
      <dc:creator>rshoward</dc:creator>
      <dc:date>2011-04-09T05:14:52Z</dc:date>
    </item>
    <item>
      <title>Re: splunk.Intersplunk.outputResults sending another header? Or bad commands.conf options?</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/splunk-Intersplunk-outputResults-sending-another-header-Or-bad/m-p/78463#M1116</link>
      <description>&lt;P&gt;That output looks very strange.&lt;/P&gt;

&lt;P&gt;I'm unsure about all the settings for your command in command.conf.  &lt;/P&gt;

&lt;P&gt;I'm also unsure what your command is doing with the _time values -- whether it's casting them to a string, for example.&lt;/P&gt;

&lt;P&gt;This would be putting a bandaid on cancer, but you might want to look at the generates_timeorder and overrides_timeorder settings for your command in commands.conf.&lt;/P&gt;</description>
      <pubDate>Thu, 14 Apr 2011 11:04:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/splunk-Intersplunk-outputResults-sending-another-header-Or-bad/m-p/78463#M1116</guid>
      <dc:creator>carasso</dc:creator>
      <dc:date>2011-04-14T11:04:53Z</dc:date>
    </item>
    <item>
      <title>Re: splunk.Intersplunk.outputResults sending another header? Or bad commands.conf options?</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/splunk-Intersplunk-outputResults-sending-another-header-Or-bad/m-p/78464#M1117</link>
      <description>&lt;P&gt;this was all in my fast and flustered attempt at getting my first streaming command, and first python code (Yes I've been living under a rock, but only renting), to run before the weekend.&lt;/P&gt;

&lt;P&gt;I ended up with &lt;A href="http://answers.splunk.com/questions/13636/calculate-entropy-just-entropy-not-change-in-entropy-like-associate/13701#13701"&gt;http://answers.splunk.com/questions/13636/calculate-entropy-just-entropy-not-change-in-entropy-like-associate/13701#13701&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;I came to the conclusion that I might have been using the functions completely backwards. (bulk for streaming etc)&lt;/P&gt;</description>
      <pubDate>Thu, 14 Apr 2011 23:24:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/splunk-Intersplunk-outputResults-sending-another-header-Or-bad/m-p/78464#M1117</guid>
      <dc:creator>rshoward</dc:creator>
      <dc:date>2011-04-14T23:24:44Z</dc:date>
    </item>
  </channel>
</rss>

