<?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: regex formation in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/regex-formation/m-p/23002#M177441</link>
    <description>&lt;P&gt;If you could post an example event one of the community or myself could probably write a regex for you&lt;/P&gt;</description>
    <pubDate>Fri, 02 Aug 2013 08:36:23 GMT</pubDate>
    <dc:creator>Drainy</dc:creator>
    <dc:date>2013-08-02T08:36:23Z</dc:date>
    <item>
      <title>regex formation</title>
      <link>https://community.splunk.com/t5/Splunk-Search/regex-formation/m-p/23001#M177440</link>
      <description>&lt;P&gt;hi,&lt;BR /&gt;
in my log files there is a field name cpu time with different time values like 57.682 sec,0.572 sec and among the highest it is 1133.982 secs when i am trying to extract 1133.982,it showing me the message..&lt;/P&gt;

&lt;P&gt;&lt;EM&gt;No regex could be learned. Try providing different examples or restriction&lt;/EM&gt; &lt;BR /&gt;
so how can i extract this field&lt;/P&gt;</description>
      <pubDate>Fri, 02 Aug 2013 05:15:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/regex-formation/m-p/23001#M177440</guid>
      <dc:creator>harsh1734</dc:creator>
      <dc:date>2013-08-02T05:15:55Z</dc:date>
    </item>
    <item>
      <title>Re: regex formation</title>
      <link>https://community.splunk.com/t5/Splunk-Search/regex-formation/m-p/23002#M177441</link>
      <description>&lt;P&gt;If you could post an example event one of the community or myself could probably write a regex for you&lt;/P&gt;</description>
      <pubDate>Fri, 02 Aug 2013 08:36:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/regex-formation/m-p/23002#M177441</guid>
      <dc:creator>Drainy</dc:creator>
      <dc:date>2013-08-02T08:36:23Z</dc:date>
    </item>
    <item>
      <title>Re: regex formation</title>
      <link>https://community.splunk.com/t5/Splunk-Search/regex-formation/m-p/23003#M177442</link>
      <description>&lt;PRE&gt;&lt;CODE&gt;... | rex "(?&amp;lt;cpu_time&amp;gt;\d+(?:\.\d+)?) sec"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This looks for a number, optionally followed by .xxxx follwowd by "sec", and sets a field called cpu_time to the number component of the string.&lt;/P&gt;</description>
      <pubDate>Fri, 02 Aug 2013 11:16:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/regex-formation/m-p/23003#M177442</guid>
      <dc:creator>jonuwz</dc:creator>
      <dc:date>2013-08-02T11:16:24Z</dc:date>
    </item>
    <item>
      <title>Re: regex formation</title>
      <link>https://community.splunk.com/t5/Splunk-Search/regex-formation/m-p/23004#M177443</link>
      <description>&lt;P&gt;Using the regex to get establish field name can be a pretty big pain.&lt;/P&gt;

&lt;P&gt;Unless there's a good reason not to, I'd recommend logging the CPU Time within the .log file as something like: "CPU_Time=1133.982" (minus the quotation marks)&lt;/P&gt;

&lt;P&gt;Splunk will automatically create the field "CPU_Time" if you log your information this way. It's extremely convenient. &lt;/P&gt;</description>
      <pubDate>Fri, 02 Aug 2013 12:55:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/regex-formation/m-p/23004#M177443</guid>
      <dc:creator>mothmen</dc:creator>
      <dc:date>2013-08-02T12:55:23Z</dc:date>
    </item>
  </channel>
</rss>

