<?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: Convert field extraction into summarized value in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Convert-field-extraction-into-summarized-value/m-p/48846#M11685</link>
    <description>&lt;P&gt;You could use &lt;CODE&gt;eval&lt;/CODE&gt;. Let's say you extracted the values "Sending" and "Received", respectively:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;... | eval dir_type=case(Direction,"Sending","Outbound","Received","Inbound")
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Fri, 31 Aug 2012 18:58:35 GMT</pubDate>
    <dc:creator>Ayn</dc:creator>
    <dc:date>2012-08-31T18:58:35Z</dc:date>
    <item>
      <title>Convert field extraction into summarized value</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Convert-field-extraction-into-summarized-value/m-p/48845#M11684</link>
      <description>&lt;P&gt;Hi there,&lt;/P&gt;

&lt;P&gt;I have a log that prefaces each message with either "Sending data on connection" or "Received data on connection".  I have created an extraction to extract this value as "Direction", but I'd like to be able to show that result in a table as simply "Inbound" or "Outbound".   Can anyone point me in the right direction for this?&lt;/P&gt;

&lt;P&gt;Thanks in advance,&lt;/P&gt;

&lt;P&gt;Brandon&lt;/P&gt;</description>
      <pubDate>Fri, 31 Aug 2012 18:47:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Convert-field-extraction-into-summarized-value/m-p/48845#M11684</guid>
      <dc:creator>branfarm</dc:creator>
      <dc:date>2012-08-31T18:47:22Z</dc:date>
    </item>
    <item>
      <title>Re: Convert field extraction into summarized value</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Convert-field-extraction-into-summarized-value/m-p/48846#M11685</link>
      <description>&lt;P&gt;You could use &lt;CODE&gt;eval&lt;/CODE&gt;. Let's say you extracted the values "Sending" and "Received", respectively:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;... | eval dir_type=case(Direction,"Sending","Outbound","Received","Inbound")
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Fri, 31 Aug 2012 18:58:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Convert-field-extraction-into-summarized-value/m-p/48846#M11685</guid>
      <dc:creator>Ayn</dc:creator>
      <dc:date>2012-08-31T18:58:35Z</dc:date>
    </item>
    <item>
      <title>Re: Convert field extraction into summarized value</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Convert-field-extraction-into-summarized-value/m-p/48847#M11686</link>
      <description>&lt;P&gt;Thanks, Ayn.  That worked, but seems very cumbersome in the search.  Would a lookup table be able to accomplish this and keep the usability?  For instance, enabling a user to use a search including direction=inbound ?&lt;/P&gt;</description>
      <pubDate>Fri, 31 Aug 2012 19:08:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Convert-field-extraction-into-summarized-value/m-p/48847#M11686</guid>
      <dc:creator>branfarm</dc:creator>
      <dc:date>2012-08-31T19:08:48Z</dc:date>
    </item>
    <item>
      <title>Re: Convert field extraction into summarized value</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Convert-field-extraction-into-summarized-value/m-p/48848#M11687</link>
      <description>&lt;P&gt;Yes, you could use a lookup table for that. Also, in Splunk 5.0 that is due out...sometime in the future, you can setup eval statements in configuration files!&lt;/P&gt;</description>
      <pubDate>Fri, 31 Aug 2012 19:51:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Convert-field-extraction-into-summarized-value/m-p/48848#M11687</guid>
      <dc:creator>Ayn</dc:creator>
      <dc:date>2012-08-31T19:51:40Z</dc:date>
    </item>
  </channel>
</rss>

