<?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: Stuck on extracting fields using own RegEx in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Stuck-on-extracting-fields-using-own-RegEx/m-p/318651#M95306</link>
    <description>&lt;P&gt;@StuReeves... Happens to all of us... all the time! Glad it worked &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 11 Apr 2017 12:29:08 GMT</pubDate>
    <dc:creator>niketn</dc:creator>
    <dc:date>2017-04-11T12:29:08Z</dc:date>
    <item>
      <title>Stuck on extracting fields using own RegEx</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Stuck-on-extracting-fields-using-own-RegEx/m-p/318648#M95303</link>
      <description>&lt;P&gt;Hi, still finding my around Spplunk and I've sort of go what I want in pt2 of my requirements, but after a couple of days, I'm just going around in a spin.&lt;/P&gt;

&lt;P&gt;I'm trying to split up the raw data from an Avaya CM. I've go it coming in, managed to break each entry into a single line but then I get stumped trying to break it up further using the Extract Fields. I presume I need to ad this to either props or transforms, but at a loss what I need to enter.&lt;/P&gt;

&lt;P&gt;The Avaya data comes in a fixed format such as:&lt;/P&gt;

&lt;P&gt;and so on.&lt;/P&gt;

&lt;P&gt;Using rex101 I created the expression&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;^(.{6})\s(.{4})\s(.{5})\s(.{1})\s(.{4})\s(.{4})\s(.{18})\s(.{15})\s(.{4})\s(.{7})\s(.{3})\s(.{3})\s(.{11})\s(.{5})\s(.{15})\s(.{2})\s(.{6})
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;which seems to work pefectly in the test.&lt;/P&gt;

&lt;P&gt;However I'm at a complete loss as where to go next so that each field is split up and named. I've always used the Field Extraction tool, but it's the 1st time I've tried using my own, as opposed to standard delimiters.&lt;BR /&gt;
All that I get is a tick next to my values, but can't do anything from there.&lt;BR /&gt;
Sure it's something pretty simple, but I'm just stumped.&lt;BR /&gt;
Thanks once again&lt;BR /&gt;
Stu..&lt;/P&gt;</description>
      <pubDate>Tue, 11 Apr 2017 12:02:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Stuck-on-extracting-fields-using-own-RegEx/m-p/318648#M95303</guid>
      <dc:creator>StuReeves</dc:creator>
      <dc:date>2017-04-11T12:02:07Z</dc:date>
    </item>
    <item>
      <title>Re: Stuck on extracting fields using own RegEx</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Stuck-on-extracting-fields-using-own-RegEx/m-p/318649#M95304</link>
      <description>&lt;P&gt;@StuReevs... Since you have not attached mock data in the question... I would expect the following to work. You seem to be missing names for extracted fields, Please test yourself in &lt;STRONG&gt;regex101&lt;/STRONG&gt; first. You can also test the same in Splunk using &lt;STRONG&gt;rex&lt;/STRONG&gt; SPL command. Please change the field names from &lt;STRONG&gt;field1&lt;/STRONG&gt; thru &lt;STRONG&gt;field17&lt;/STRONG&gt; to something meaningful based on what you need.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;^(?&amp;lt;field1&amp;gt;.{6})\s(?&amp;lt;field2&amp;gt;.{4})\s(?&amp;lt;field3&amp;gt;.{5})\s(?&amp;lt;field4&amp;gt;.{1})\s(?&amp;lt;field5&amp;gt;.{4})\s(?&amp;lt;field6&amp;gt;.{4})\s(?&amp;lt;field7&amp;gt;.{18})\s(?&amp;lt;field8&amp;gt;.{15})\s(?&amp;lt;field9&amp;gt;.{4})\s(?&amp;lt;field10&amp;gt;.{7})\s(?&amp;lt;field11&amp;gt;.{3})\s(?&amp;lt;field12&amp;gt;.{3})\s(?&amp;lt;field13&amp;gt;.{11})\s(?&amp;lt;field14&amp;gt;.{5})\s(?&amp;lt;field15&amp;gt;.{15})\s(?&amp;lt;field16&amp;gt;.{2})\s(?&amp;lt;field17&amp;gt;.{6})
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Tue, 11 Apr 2017 12:15:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Stuck-on-extracting-fields-using-own-RegEx/m-p/318649#M95304</guid>
      <dc:creator>niketn</dc:creator>
      <dc:date>2017-04-11T12:15:52Z</dc:date>
    </item>
    <item>
      <title>Re: Stuck on extracting fields using own RegEx</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Stuck-on-extracting-fields-using-own-RegEx/m-p/318650#M95305</link>
      <description>&lt;P&gt;Thats done the trick. I knew it was something fairly simple I was missing.&lt;/P&gt;</description>
      <pubDate>Tue, 11 Apr 2017 12:26:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Stuck-on-extracting-fields-using-own-RegEx/m-p/318650#M95305</guid>
      <dc:creator>StuReeves</dc:creator>
      <dc:date>2017-04-11T12:26:47Z</dc:date>
    </item>
    <item>
      <title>Re: Stuck on extracting fields using own RegEx</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Stuck-on-extracting-fields-using-own-RegEx/m-p/318651#M95306</link>
      <description>&lt;P&gt;@StuReeves... Happens to all of us... all the time! Glad it worked &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 11 Apr 2017 12:29:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Stuck-on-extracting-fields-using-own-RegEx/m-p/318651#M95306</guid>
      <dc:creator>niketn</dc:creator>
      <dc:date>2017-04-11T12:29:08Z</dc:date>
    </item>
  </channel>
</rss>

