<?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: Single Event vs. multi-events for scripted inputs in All Apps and Add-ons</title>
    <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Single-Event-vs-multi-events-for-scripted-inputs/m-p/98146#M6771</link>
    <description>&lt;P&gt;Odd, source=cpu is still showing up as a single event for me.  But  the question was more "why the change", it kinda made sense to have one event as it's a snapshot in time, but yea always having to "| multikv" is a pain.  Just trying to understand the reasoning, to mirror the functionality on my own inputs.&lt;/P&gt;</description>
    <pubDate>Mon, 14 Oct 2013 22:33:39 GMT</pubDate>
    <dc:creator>mikelanghorst</dc:creator>
    <dc:date>2013-10-14T22:33:39Z</dc:date>
    <item>
      <title>Single Event vs. multi-events for scripted inputs</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Single-Event-vs-multi-events-for-scripted-inputs/m-p/98144#M6769</link>
      <description>&lt;P&gt;Previously the scripted inputs (source=cpu, source=netstat, etc) all created a single event per run.  Recently however I noticed the openports (was probably that way for awhile) creates an event per line of output.&lt;/P&gt;

&lt;P&gt;Why the differences?  Just trying to understand the reason behind one vs. the other.&lt;/P&gt;</description>
      <pubDate>Mon, 14 Oct 2013 21:32:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Single-Event-vs-multi-events-for-scripted-inputs/m-p/98144#M6769</guid>
      <dc:creator>mikelanghorst</dc:creator>
      <dc:date>2013-10-14T21:32:30Z</dc:date>
    </item>
    <item>
      <title>Re: Single Event vs. multi-events for scripted inputs</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Single-Event-vs-multi-events-for-scripted-inputs/m-p/98145#M6770</link>
      <description>&lt;P&gt;This is not new.&lt;BR /&gt;
The props.conf config in older and current versions calls for a single line per event.&lt;/P&gt;

&lt;P&gt;in unix app 4.6&lt;BR /&gt;
&lt;CODE&gt;&lt;BR /&gt;
[cpu]&lt;BR /&gt;
SHOULD_LINEMERGE=false&lt;BR /&gt;
LINE_BREAKER=^()$&lt;BR /&gt;
TRUNCATE=1000000&lt;BR /&gt;
DATETIME_CONFIG = CURRENT&lt;BR /&gt;
REPORT-fields_for_cpu_sh = fields_for_cpu_sh&lt;BR /&gt;
&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;in unix app 5.0.0&lt;BR /&gt;
`&lt;BR /&gt;
[cpu]&lt;BR /&gt;
SHOULD_LINEMERGE=false&lt;BR /&gt;
LINE_BREAKER=(^$|[\r\n]+[\r\n]+)&lt;BR /&gt;
TRUNCATE=1000000&lt;BR /&gt;
DATETIME_CONFIG = CURRENT&lt;BR /&gt;
KV_MODE = multi&lt;BR /&gt;
FIELDALIAS-dest_for_cpu = host as dest&lt;BR /&gt;
FIELDALIAS-src_for_cpu = host as src&lt;BR /&gt;
FIELDALIAS-cpu_for_cpu = CPU as cpu&lt;BR /&gt;
FIELDALIAS-idle_time_for_cpu = pctIdle AS PercentIdleTime&lt;BR /&gt;
FIELDALIAS-nice_time_for_cpu = pctNice AS PercentNiceTime&lt;BR /&gt;
FIELDALIAS-cpu_load_percent_for_cpu = pctSystem AS PercentSystemTime,pctSystem as cpu_load_percent&lt;BR /&gt;
FIELDALIAS-cpu_user_percent_for_cpu = pctUser AS PercentUserTime,pctUser as cpu_user_percent&lt;BR /&gt;
FIELDALIAS-wait_time_for_cpu = pctIowait AS PercentWaitTime&lt;/P&gt;

&lt;P&gt;`&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 14:57:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Single-Event-vs-multi-events-for-scripted-inputs/m-p/98145#M6770</guid>
      <dc:creator>yannK</dc:creator>
      <dc:date>2020-09-28T14:57:57Z</dc:date>
    </item>
    <item>
      <title>Re: Single Event vs. multi-events for scripted inputs</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Single-Event-vs-multi-events-for-scripted-inputs/m-p/98146#M6771</link>
      <description>&lt;P&gt;Odd, source=cpu is still showing up as a single event for me.  But  the question was more "why the change", it kinda made sense to have one event as it's a snapshot in time, but yea always having to "| multikv" is a pain.  Just trying to understand the reasoning, to mirror the functionality on my own inputs.&lt;/P&gt;</description>
      <pubDate>Mon, 14 Oct 2013 22:33:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Single-Event-vs-multi-events-for-scripted-inputs/m-p/98146#M6771</guid>
      <dc:creator>mikelanghorst</dc:creator>
      <dc:date>2013-10-14T22:33:39Z</dc:date>
    </item>
    <item>
      <title>Re: Single Event vs. multi-events for scripted inputs</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Single-Event-vs-multi-events-for-scripted-inputs/m-p/98147#M6772</link>
      <description>&lt;P&gt;Though I've not updated to the TA for my *nix inputs yet, will roll that into my 6.0 upgrade.&lt;/P&gt;</description>
      <pubDate>Mon, 14 Oct 2013 22:36:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Single-Event-vs-multi-events-for-scripted-inputs/m-p/98147#M6772</guid>
      <dc:creator>mikelanghorst</dc:creator>
      <dc:date>2013-10-14T22:36:01Z</dc:date>
    </item>
  </channel>
</rss>

