<?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: Searching for punct field values in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Searching-for-punct-field-values/m-p/149461#M41808</link>
    <description>&lt;P&gt;You need to escape double quotes and backslashes with a backslash, then you can search for &lt;CODE&gt;punct&lt;/CODE&gt; values like any other &lt;CODE&gt;field="value"&lt;/CODE&gt;.&lt;/P&gt;</description>
    <pubDate>Thu, 01 May 2014 21:38:52 GMT</pubDate>
    <dc:creator>martin_mueller</dc:creator>
    <dc:date>2014-05-01T21:38:52Z</dc:date>
    <item>
      <title>Searching for punct field values</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Searching-for-punct-field-values/m-p/149459#M41806</link>
      <description>&lt;P&gt;As the title reveals, I am trying to search the punct field for specific values.  The punct field is naturally tricky because it includes quotation marks, dashes, and other unique characters which naturally yield search errors or throw off the search.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;The search below is most likely incorrect but serves to clarify the task and an example string including problematic characters:&lt;/STRONG&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| search punct="___::_..__--::_..__-_-_-___:__="_':\__()\_\_\.\\.'"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The most obvious problem with this string is the double quotation mark in the middle of the string.  These strings vary in form with each event record and different strings may be desired for the punct search.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;In summary, how do I search the event records for specific punct field values?&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 01 May 2014 20:13:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Searching-for-punct-field-values/m-p/149459#M41806</guid>
      <dc:creator>landen99</dc:creator>
      <dc:date>2014-05-01T20:13:48Z</dc:date>
    </item>
    <item>
      <title>Re: Searching for punct field values</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Searching-for-punct-field-values/m-p/149460#M41807</link>
      <description>&lt;P&gt;Based on the punct values I see in my logs, double qoutes is the only problematic character. You can escape it with a backward slash (\). How are you providing your punct filters, through dashboard/form input?&lt;/P&gt;</description>
      <pubDate>Thu, 01 May 2014 21:35:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Searching-for-punct-field-values/m-p/149460#M41807</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2014-05-01T21:35:41Z</dc:date>
    </item>
    <item>
      <title>Re: Searching for punct field values</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Searching-for-punct-field-values/m-p/149461#M41808</link>
      <description>&lt;P&gt;You need to escape double quotes and backslashes with a backslash, then you can search for &lt;CODE&gt;punct&lt;/CODE&gt; values like any other &lt;CODE&gt;field="value"&lt;/CODE&gt;.&lt;/P&gt;</description>
      <pubDate>Thu, 01 May 2014 21:38:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Searching-for-punct-field-values/m-p/149461#M41808</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2014-05-01T21:38:52Z</dc:date>
    </item>
    <item>
      <title>Re: Searching for punct field values</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Searching-for-punct-field-values/m-p/149462#M41809</link>
      <description>&lt;P&gt;Are you saying that the search for the string in the field above would look like this?:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| search punct="___::_..__--::_..__-_-_-___:__=\"_':\\__()\\_\\_\\.\\\\.'"
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Fri, 02 May 2014 11:57:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Searching-for-punct-field-values/m-p/149462#M41809</guid>
      <dc:creator>landen99</dc:creator>
      <dc:date>2014-05-02T11:57:47Z</dc:date>
    </item>
    <item>
      <title>Re: Searching for punct field values</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Searching-for-punct-field-values/m-p/149463#M41810</link>
      <description>&lt;P&gt;This is for a normal search (currently).&lt;/P&gt;</description>
      <pubDate>Fri, 02 May 2014 11:58:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Searching-for-punct-field-values/m-p/149463#M41810</guid>
      <dc:creator>landen99</dc:creator>
      <dc:date>2014-05-02T11:58:16Z</dc:date>
    </item>
    <item>
      <title>Re: Searching for punct field values</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Searching-for-punct-field-values/m-p/149464#M41811</link>
      <description>&lt;P&gt;If that's your entire search then you should leave off the &lt;CODE&gt;| search&lt;/CODE&gt;.&lt;/P&gt;</description>
      <pubDate>Fri, 02 May 2014 13:03:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Searching-for-punct-field-values/m-p/149464#M41811</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2014-05-02T13:03:27Z</dc:date>
    </item>
  </channel>
</rss>

