<?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 Filtering out header-only &amp;quot;events&amp;quot; after using MultiKV in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Filtering-out-header-only-quot-events-quot-after-using-MultiKV/m-p/94889#M19756</link>
    <description>&lt;P&gt;I've been tweaking the *NIX app by adding some charts with queries such as:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index="os" sourcetype="who" host=$host$ | multikv | timechart count by USERNAME
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The resulting chart has a large number of events where the USERNAME is NULL. This appears to be because the MultiKV command only filters out the header when there is a body in the event. If the "who" event only contains a header the MultiKV leaves it in the result set as an event.&lt;/P&gt;

&lt;P&gt;What is the best way to get rid of these unwanted header "events"? I would prefer to index them, as then there is a contiguous record from the who script. I could use&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index="os" sourcetype="who" | multikv | search _raw!="*USERNAME        LINE        HOSTNAME                                  TIME*"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;however there are likely many other similar situations so a more generic solution would be helpful.&lt;/P&gt;

&lt;P&gt;Is there a better way?&lt;/P&gt;

&lt;P&gt;Thanks.&lt;/P&gt;</description>
    <pubDate>Fri, 26 Nov 2010 11:15:49 GMT</pubDate>
    <dc:creator>FunPolice</dc:creator>
    <dc:date>2010-11-26T11:15:49Z</dc:date>
    <item>
      <title>Filtering out header-only "events" after using MultiKV</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Filtering-out-header-only-quot-events-quot-after-using-MultiKV/m-p/94889#M19756</link>
      <description>&lt;P&gt;I've been tweaking the *NIX app by adding some charts with queries such as:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index="os" sourcetype="who" host=$host$ | multikv | timechart count by USERNAME
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The resulting chart has a large number of events where the USERNAME is NULL. This appears to be because the MultiKV command only filters out the header when there is a body in the event. If the "who" event only contains a header the MultiKV leaves it in the result set as an event.&lt;/P&gt;

&lt;P&gt;What is the best way to get rid of these unwanted header "events"? I would prefer to index them, as then there is a contiguous record from the who script. I could use&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index="os" sourcetype="who" | multikv | search _raw!="*USERNAME        LINE        HOSTNAME                                  TIME*"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;however there are likely many other similar situations so a more generic solution would be helpful.&lt;/P&gt;

&lt;P&gt;Is there a better way?&lt;/P&gt;

&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Fri, 26 Nov 2010 11:15:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Filtering-out-header-only-quot-events-quot-after-using-MultiKV/m-p/94889#M19756</guid>
      <dc:creator>FunPolice</dc:creator>
      <dc:date>2010-11-26T11:15:49Z</dc:date>
    </item>
    <item>
      <title>Re: Filtering out header-only "events" after using MultiKV</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Filtering-out-header-only-quot-events-quot-after-using-MultiKV/m-p/94890#M19757</link>
      <description>&lt;P&gt;a slightly better approach would be:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index="os" sourcetype="who" host=$host$ | multikv | search USERNAME=* | timechart count by USERNAME
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;basically filter out all results that are missing the USERNAME field&lt;/P&gt;</description>
      <pubDate>Sat, 27 Nov 2010 11:41:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Filtering-out-header-only-quot-events-quot-after-using-MultiKV/m-p/94890#M19757</guid>
      <dc:creator>Ledion_Bitincka</dc:creator>
      <dc:date>2010-11-27T11:41:57Z</dc:date>
    </item>
    <item>
      <title>Re: Filtering out header-only "events" after using MultiKV</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Filtering-out-header-only-quot-events-quot-after-using-MultiKV/m-p/94891#M19758</link>
      <description>&lt;P&gt;I just don't get this behavior. &lt;CODE&gt;multikv&lt;/CODE&gt; for me simply doesn't return the header rows, so I don't get this problem.&lt;/P&gt;</description>
      <pubDate>Tue, 30 Nov 2010 06:06:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Filtering-out-header-only-quot-events-quot-after-using-MultiKV/m-p/94891#M19758</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2010-11-30T06:06:12Z</dc:date>
    </item>
    <item>
      <title>Re: Filtering out header-only "events" after using MultiKV</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Filtering-out-header-only-quot-events-quot-after-using-MultiKV/m-p/94892#M19759</link>
      <description>&lt;P&gt;I've upgraded to 4.2 and will try again with the universal forwarder as soon as I get a chance. Stay tuned!&lt;/P&gt;</description>
      <pubDate>Mon, 23 May 2011 22:45:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Filtering-out-header-only-quot-events-quot-after-using-MultiKV/m-p/94892#M19759</guid>
      <dc:creator>FunPolice</dc:creator>
      <dc:date>2011-05-23T22:45:18Z</dc:date>
    </item>
  </channel>
</rss>

