<?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 Unique CSV Regex- Process Alarm issue? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Unique-CSV-Regex-Process-Alarm-issue/m-p/650443#M110521</link>
    <description>&lt;P&gt;I have raw data file (similar to a CSV) with various records as follows:&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Process alarm,5/31/2023,23:19:45,20,11PC_0201,# 2 BOILER STEAM DRUM PRESSURE,Medium,L-Lower Limit,South Main,110.0,110.0,PSIG&lt;/P&gt;
&lt;P&gt;Process alarm,5/31/2023,22:45:07,34,25N_0004,CP - 5kV BREAKERALARMS,Medium,TIE-BRKR CLOSED,Common Signal&lt;/P&gt;
&lt;P&gt;In my transforms.conf file:&lt;/P&gt;
&lt;P&gt;[parseProcessAlarm]&lt;BR /&gt;REGEX = Process alarm,([^,]+),([^,]+),([^,]+),([^,]+),([^,]+),([^,]+),([^,]+),([^,]+),([^,]+),([^,]+),([^,]+)&lt;BR /&gt;FORMAT = Date::$1 TimeStamp::$2 TagType::$3 Tagname::$4 Description::$5 AlarmSeverity::$6 AlarmName::$7 SignalCategory::$8 Data::$9 LimitData::$10 EngineeringUnits::$11&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;My problem is that this expression fails sometimes because a "Process Alarm" record may only have 8 data fields after the initial "Process Alarm" wording as shown above. How can I account for this?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 13 Jul 2023 20:38:11 GMT</pubDate>
    <dc:creator>teco_akelly</dc:creator>
    <dc:date>2023-07-13T20:38:11Z</dc:date>
    <item>
      <title>Unique CSV Regex- Process Alarm issue?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Unique-CSV-Regex-Process-Alarm-issue/m-p/650443#M110521</link>
      <description>&lt;P&gt;I have raw data file (similar to a CSV) with various records as follows:&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Process alarm,5/31/2023,23:19:45,20,11PC_0201,# 2 BOILER STEAM DRUM PRESSURE,Medium,L-Lower Limit,South Main,110.0,110.0,PSIG&lt;/P&gt;
&lt;P&gt;Process alarm,5/31/2023,22:45:07,34,25N_0004,CP - 5kV BREAKERALARMS,Medium,TIE-BRKR CLOSED,Common Signal&lt;/P&gt;
&lt;P&gt;In my transforms.conf file:&lt;/P&gt;
&lt;P&gt;[parseProcessAlarm]&lt;BR /&gt;REGEX = Process alarm,([^,]+),([^,]+),([^,]+),([^,]+),([^,]+),([^,]+),([^,]+),([^,]+),([^,]+),([^,]+),([^,]+)&lt;BR /&gt;FORMAT = Date::$1 TimeStamp::$2 TagType::$3 Tagname::$4 Description::$5 AlarmSeverity::$6 AlarmName::$7 SignalCategory::$8 Data::$9 LimitData::$10 EngineeringUnits::$11&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;My problem is that this expression fails sometimes because a "Process Alarm" record may only have 8 data fields after the initial "Process Alarm" wording as shown above. How can I account for this?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 13 Jul 2023 20:38:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Unique-CSV-Regex-Process-Alarm-issue/m-p/650443#M110521</guid>
      <dc:creator>teco_akelly</dc:creator>
      <dc:date>2023-07-13T20:38:11Z</dc:date>
    </item>
    <item>
      <title>Re: Unique CSV Regex- Process Alarm issue?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Unique-CSV-Regex-Process-Alarm-issue/m-p/650482#M110523</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/230217"&gt;@teco_akelly&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;you should try to configure two regexes for both the cases,&amp;nbsp;&lt;/P&gt;&lt;P&gt;then you should see if at least one regex extracts the correct values, otherwise, you could give a diferent name (e.g. Date1 and Date2) and use eval and coalesce to choose the correct one.&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Fri, 14 Jul 2023 06:26:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Unique-CSV-Regex-Process-Alarm-issue/m-p/650482#M110523</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2023-07-14T06:26:56Z</dc:date>
    </item>
    <item>
      <title>Re: Unique CSV Regex- Process Alarm issue?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Unique-CSV-Regex-Process-Alarm-issue/m-p/650503#M110526</link>
      <description>&lt;P&gt;Try something like this&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[parseProcessAlarm]
REGEX = Process alarm,([^,]+),([^,]+),([^,]+),([^,]+),([^,]+),([^,]+),([^,]+),([^,]+)(,([^,]+),([^,]+),([^,]+)|)
FORMAT = Date::$1 TimeStamp::$2 TagType::$3 Tagname::$4 Description::$5 AlarmSeverity::$6 AlarmName::$7 SignalCategory::$8 Data::$10 LimitData::$11 EngineeringUnits::$12&lt;/LI-CODE&gt;&lt;P&gt;Essentially, make the last three capture groups part of another capture group which has an empty alternative, then bump the last three references by 1 i.e. $10, $11, $12&lt;/P&gt;</description>
      <pubDate>Fri, 14 Jul 2023 07:55:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Unique-CSV-Regex-Process-Alarm-issue/m-p/650503#M110526</guid>
      <dc:creator>ITWhisperer</dc:creator>
      <dc:date>2023-07-14T07:55:01Z</dc:date>
    </item>
    <item>
      <title>Re: Unique CSV Regex- Process Alarm issue?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Unique-CSV-Regex-Process-Alarm-issue/m-p/651126#M110598</link>
      <description>&lt;P&gt;Is there a way to make the wording "Process alarm" into a field? I have many more other log entry types and would like to make them a searchable field.&lt;/P&gt;</description>
      <pubDate>Wed, 19 Jul 2023 13:52:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Unique-CSV-Regex-Process-Alarm-issue/m-p/651126#M110598</guid>
      <dc:creator>teco_akelly</dc:creator>
      <dc:date>2023-07-19T13:52:13Z</dc:date>
    </item>
    <item>
      <title>Re: Unique CSV Regex- Process Alarm issue?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Unique-CSV-Regex-Process-Alarm-issue/m-p/651134#M110599</link>
      <description>&lt;P&gt;Add a new capture group at the beginning and increment all the references by 1&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[parseProcessAlarm]
REGEX = (Process alarm),([^,]+),([^,]+),([^,]+),([^,]+),([^,]+),([^,]+),([^,]+),([^,]+)(,([^,]+),([^,]+),([^,]+)|)
FORMAT = Event::$1 Date::$2 TimeStamp::$3 TagType::$4 Tagname::$5 Description::$6 AlarmSeverity::$7 AlarmName::$8 SignalCategory::$9 Data::$11 LimitData::$12 EngineeringUnits::$13&lt;/LI-CODE&gt;</description>
      <pubDate>Wed, 19 Jul 2023 15:08:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Unique-CSV-Regex-Process-Alarm-issue/m-p/651134#M110599</guid>
      <dc:creator>ITWhisperer</dc:creator>
      <dc:date>2023-07-19T15:08:02Z</dc:date>
    </item>
  </channel>
</rss>

