<?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: Add description to field value in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Add-description-to-field-value/m-p/668671#M229361</link>
    <description>&lt;P&gt;Depending on how many cases you have, you can either do it inline, with&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| eval description=case(match(Message, "regex_expression1"), "Description1",
                        match(Message, "regex_expression2"), "Description2",
                        match(Message, "regex_expression3"), "Description3")&lt;/LI-CODE&gt;&lt;P&gt;or probably more practical is to make a lookup - probably a wildcard based lookup, which means creating a CSV with Message, Description fields and then a lookup DEFINITION that has the match type set to&amp;nbsp;&lt;/P&gt;&lt;P&gt;WILDCARD(Message)&lt;/P&gt;&lt;P&gt;In that you could then put things like&lt;/P&gt;&lt;P&gt;"&lt;SPAN&gt;DNS name resolution failure*" as the Message column and then a suitable description.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Using a wildcard type means you don't have to write SPL to extract particular bits of the message to determine the lookup attribute.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 15 Nov 2023 01:51:47 GMT</pubDate>
    <dc:creator>bowesmana</dc:creator>
    <dc:date>2023-11-15T01:51:47Z</dc:date>
    <item>
      <title>Add description to field value</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Add-description-to-field-value/m-p/668634#M229348</link>
      <description>&lt;P&gt;Hello,&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a system log which contains different DNS error messages (in the 'Message' field) and I am looking for an easy way to provide a short, meaningful description for those messages, either by adding a new field representing each unique DNS error message, or by adding text to the Message field.&lt;BR /&gt;&lt;BR /&gt;Here's an example; one event contains the following :&amp;nbsp;&lt;BR /&gt;Message="DNS name resolution failure (sos.epdg.epc.mnc720.mcc302.pub.3gppnetwork.org)"&lt;BR /&gt;&lt;BR /&gt;This error is related to WiFi calling, so I would like to associate a description, or tag to that specific message, e.g. "WiFi calling".&lt;BR /&gt;&lt;BR /&gt;Thoughts?&lt;/P&gt;</description>
      <pubDate>Tue, 14 Nov 2023 18:38:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Add-description-to-field-value/m-p/668634#M229348</guid>
      <dc:creator>phildefer</dc:creator>
      <dc:date>2023-11-14T18:38:43Z</dc:date>
    </item>
    <item>
      <title>Re: Add description to field value</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Add-description-to-field-value/m-p/668671#M229361</link>
      <description>&lt;P&gt;Depending on how many cases you have, you can either do it inline, with&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| eval description=case(match(Message, "regex_expression1"), "Description1",
                        match(Message, "regex_expression2"), "Description2",
                        match(Message, "regex_expression3"), "Description3")&lt;/LI-CODE&gt;&lt;P&gt;or probably more practical is to make a lookup - probably a wildcard based lookup, which means creating a CSV with Message, Description fields and then a lookup DEFINITION that has the match type set to&amp;nbsp;&lt;/P&gt;&lt;P&gt;WILDCARD(Message)&lt;/P&gt;&lt;P&gt;In that you could then put things like&lt;/P&gt;&lt;P&gt;"&lt;SPAN&gt;DNS name resolution failure*" as the Message column and then a suitable description.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Using a wildcard type means you don't have to write SPL to extract particular bits of the message to determine the lookup attribute.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 15 Nov 2023 01:51:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Add-description-to-field-value/m-p/668671#M229361</guid>
      <dc:creator>bowesmana</dc:creator>
      <dc:date>2023-11-15T01:51:47Z</dc:date>
    </item>
  </channel>
</rss>

