<?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: How to have Field Values represent other field values? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/How-to-have-Field-Values-represent-other-field-values/m-p/418181#M120276</link>
    <description>&lt;P&gt;This is a great solution for problems like this. I've converted your comment as Answer so that you can accept this. Others with similar problem would then know that a working solution is available.&lt;/P&gt;</description>
    <pubDate>Fri, 25 May 2018 15:29:05 GMT</pubDate>
    <dc:creator>somesoni2</dc:creator>
    <dc:date>2018-05-25T15:29:05Z</dc:date>
    <item>
      <title>How to have Field Values represent other field values?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-have-Field-Values-represent-other-field-values/m-p/418177#M120272</link>
      <description>&lt;P&gt;Hello all!&lt;/P&gt;

&lt;P&gt;I apologize for the oddly worded question. Currently, I have extracted fields from two separate log formats that provide different spellings of field values.&lt;/P&gt;

&lt;P&gt;Examples: &lt;/P&gt;

&lt;P&gt;Field Name: Status&lt;BR /&gt;
Field Values: ERROR, INFO, CRITICAL, err, info&lt;/P&gt;

&lt;P&gt;Since info and INFO are not the same string, this will provide two different metrics to work with. I would like to know if there is someway to merge the "info" into the "INFO" so that it's only seen as one metric. The same applies with err to ERROR as well. And, if there is no way to do this other than by a saved search, I can do that as well. Just let me know!&lt;/P&gt;

&lt;P&gt;Thanks you so much for your time!&lt;/P&gt;</description>
      <pubDate>Thu, 24 May 2018 21:01:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-have-Field-Values-represent-other-field-values/m-p/418177#M120272</guid>
      <dc:creator>thomastaylor</dc:creator>
      <dc:date>2018-05-24T21:01:15Z</dc:date>
    </item>
    <item>
      <title>Re: How to have Field Values represent other field values?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-have-Field-Values-represent-other-field-values/m-p/418178#M120273</link>
      <description>&lt;P&gt;Do the distinct field Values are finite list? If yes, you can add a case statement in your search to normalize the values. e.g.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;...| eval Status=case(match(Status,"^(?i)(ERR)"),"ERROR",match(Status,"^(?i)(INFO)"),"INFO",..other values )
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 24 May 2018 21:25:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-have-Field-Values-represent-other-field-values/m-p/418178#M120273</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2018-05-24T21:25:10Z</dc:date>
    </item>
    <item>
      <title>Re: How to have Field Values represent other field values?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-have-Field-Values-represent-other-field-values/m-p/418179#M120274</link>
      <description>&lt;P&gt;Thank you for your answer!&lt;/P&gt;

&lt;P&gt;We actually found a work-around solution where we tagged the statuses as "INFO" and "ERROR" for all the different log formats. We then did the search: &lt;CODE&gt;index="main" | timechart count by tag::status&lt;/CODE&gt; and it achieved what we wanted.&lt;/P&gt;</description>
      <pubDate>Fri, 25 May 2018 13:18:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-have-Field-Values-represent-other-field-values/m-p/418179#M120274</guid>
      <dc:creator>thomastaylor</dc:creator>
      <dc:date>2018-05-25T13:18:21Z</dc:date>
    </item>
    <item>
      <title>Re: How to have Field Values represent other field values?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-have-Field-Values-represent-other-field-values/m-p/418180#M120275</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;You can use the &lt;CODE&gt;tag&lt;/CODE&gt; or &lt;CODE&gt;alias&lt;/CODE&gt; in Splunk, that acn help you to manage and organise your data&lt;/P&gt;

&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Fri, 25 May 2018 13:33:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-have-Field-Values-represent-other-field-values/m-p/418180#M120275</guid>
      <dc:creator>TISKAR</dc:creator>
      <dc:date>2018-05-25T13:33:27Z</dc:date>
    </item>
    <item>
      <title>Re: How to have Field Values represent other field values?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-have-Field-Values-represent-other-field-values/m-p/418181#M120276</link>
      <description>&lt;P&gt;This is a great solution for problems like this. I've converted your comment as Answer so that you can accept this. Others with similar problem would then know that a working solution is available.&lt;/P&gt;</description>
      <pubDate>Fri, 25 May 2018 15:29:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-have-Field-Values-represent-other-field-values/m-p/418181#M120276</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2018-05-25T15:29:05Z</dc:date>
    </item>
  </channel>
</rss>

