<?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: linebreaking for text configuration file format in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/linebreaking-for-text-configuration-file-format/m-p/41068#M9502</link>
    <description>&lt;P&gt;I am afraid on this one i don't think it will be possible to maintain the linebreak of each ControlID event.&lt;BR /&gt;
Maybe someone else will have an idea...&lt;BR /&gt;
You should create a new question&lt;/P&gt;</description>
    <pubDate>Wed, 02 May 2012 07:50:39 GMT</pubDate>
    <dc:creator>MarioM</dc:creator>
    <dc:date>2012-05-02T07:50:39Z</dc:date>
    <item>
      <title>linebreaking for text configuration file format</title>
      <link>https://community.splunk.com/t5/Splunk-Search/linebreaking-for-text-configuration-file-format/m-p/41063#M9497</link>
      <description>&lt;P&gt;I am trying to linebreak my text format configuration file into the different events by the controlID. I need help in the linebreaking of my data.&lt;/P&gt;

&lt;P&gt;My text configuration looks something like this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;******************************************************************************
* Reading information for ControlID:     999999                              *
******************************************************************************

Auditing Enabled:                                           Blah
Audit Process Tracking:                                     Blah 


******************************************************************************
* Reading information for ControlID:     999999                              *
******************************************************************************

Auditing Enabled:                                           Blah
Audit Account Logon Events:                                 Blah 


******************************************************************************
* Reading information for ControlID:     999999                              *
******************************************************************************

Auditing Enabled:                                           Blah
Audit Account Management/User and Group Mgmt:               Blah 


******************************************************************************
* Reading information for ControlID:     999999                              *
******************************************************************************

Auditing Enabled:                                           Blah
Audit Logon Events/Logon and Logoff :                       Blah 
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The grey lines you see are actually ******** in my text file.&lt;/P&gt;

&lt;P&gt;I am rather new to SPLUNK and i urgently need your help in linebreaking my data. I have tried several methods but it doesn't seem to be working for my data. &lt;/P&gt;

&lt;P&gt;When i input this file into SPLUNK, it automically breaks my data into events. However, it does not break the events into what i want,it simply selects random lines to break the data,it gives no meanings to the different events.&lt;/P&gt;

&lt;P&gt;Please help me! Thank you.&lt;/P&gt;</description>
      <pubDate>Wed, 02 May 2012 03:52:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/linebreaking-for-text-configuration-file-format/m-p/41063#M9497</guid>
      <dc:creator>JeffTanYH</dc:creator>
      <dc:date>2012-05-02T03:52:06Z</dc:date>
    </item>
    <item>
      <title>Re: linebreaking for text configuration file format</title>
      <link>https://community.splunk.com/t5/Splunk-Search/linebreaking-for-text-configuration-file-format/m-p/41064#M9498</link>
      <description>&lt;P&gt;Did you try the following for your sourcetype on your props.conf:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;    [my_sourcetype]
    BREAK_ONLY_BEFORE=(.*\bControlID:.*)
    SHOULD_LINEMERGE=true
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 02 May 2012 06:52:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/linebreaking-for-text-configuration-file-format/m-p/41064#M9498</guid>
      <dc:creator>MarioM</dc:creator>
      <dc:date>2012-05-02T06:52:32Z</dc:date>
    </item>
    <item>
      <title>Re: linebreaking for text configuration file format</title>
      <link>https://community.splunk.com/t5/Splunk-Search/linebreaking-for-text-configuration-file-format/m-p/41065#M9499</link>
      <description>&lt;P&gt;Even better than &lt;CODE&gt;BREAK_ONLY_BEFORE&lt;/CODE&gt; ( SHOULD_LINEMERGE=true use more resources):&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[my_sourcetype]
LINE_BREAKER=([\r\n\-]+)\s+Reading.*
SHOULD_LINEMERGE=false
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 02 May 2012 07:12:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/linebreaking-for-text-configuration-file-format/m-p/41065#M9499</guid>
      <dc:creator>MarioM</dc:creator>
      <dc:date>2012-05-02T07:12:34Z</dc:date>
    </item>
    <item>
      <title>Re: linebreaking for text configuration file format</title>
      <link>https://community.splunk.com/t5/Splunk-Search/linebreaking-for-text-configuration-file-format/m-p/41066#M9500</link>
      <description>&lt;P&gt;And one more thing.. Could you help me figure out how do i linebreak this as well?&lt;/P&gt;

&lt;P&gt;It is feasible to break [1] from [2] and make them seperate events? While maintaining the linebreak of each ControlID event? And how?&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;******************************************************************************
* Reading information for ControlID:     999999                              *
******************************************************************************


    ________________________________________________________________________
    Object: C:\WINDOWS
    Owner:  BUILTIN\Administrators
    Group:  BUILTIN\Administrators

    ACL (DACL): 
    =========== 
    [1]:
    BUILTIN\Users
    ACE Header Type : 0x0
    ACE Header Flags: 0x0
    ACE Access Mask : 0x999999
    Apply to : [This folder] 
    Allow
        Read Permissions
        Read Extended Attributes
        Read Attributes
        List Folder/Read Data
        Traverse Folder/Execute File
    [2]:
    BUILTIN\Users
    ACE Header Type : 0x0
    ACE Header Flags: 0xb
    ACE Access Mask : 0xn0000000
    Apply to : [Subfolders] [Files] 
    Allow
        Read
        Execute
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;It would be much appreciated if you could help me!&lt;/P&gt;</description>
      <pubDate>Wed, 02 May 2012 07:19:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/linebreaking-for-text-configuration-file-format/m-p/41066#M9500</guid>
      <dc:creator>JeffTanYH</dc:creator>
      <dc:date>2012-05-02T07:19:08Z</dc:date>
    </item>
    <item>
      <title>Re: linebreaking for text configuration file format</title>
      <link>https://community.splunk.com/t5/Splunk-Search/linebreaking-for-text-configuration-file-format/m-p/41067#M9501</link>
      <description>&lt;P&gt;Hey. Thanks for your answers,greatly appreciated. The first one works better as it correctly breaks the event into the ControlID i need. The second one,however,breaks the "Auditing Enabled: Blah Audit Process Tracking: Blah " section with the ControlID below it,which is not what i want.&lt;/P&gt;</description>
      <pubDate>Wed, 02 May 2012 07:30:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/linebreaking-for-text-configuration-file-format/m-p/41067#M9501</guid>
      <dc:creator>JeffTanYH</dc:creator>
      <dc:date>2012-05-02T07:30:46Z</dc:date>
    </item>
    <item>
      <title>Re: linebreaking for text configuration file format</title>
      <link>https://community.splunk.com/t5/Splunk-Search/linebreaking-for-text-configuration-file-format/m-p/41068#M9502</link>
      <description>&lt;P&gt;I am afraid on this one i don't think it will be possible to maintain the linebreak of each ControlID event.&lt;BR /&gt;
Maybe someone else will have an idea...&lt;BR /&gt;
You should create a new question&lt;/P&gt;</description>
      <pubDate>Wed, 02 May 2012 07:50:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/linebreaking-for-text-configuration-file-format/m-p/41068#M9502</guid>
      <dc:creator>MarioM</dc:creator>
      <dc:date>2012-05-02T07:50:39Z</dc:date>
    </item>
    <item>
      <title>Re: linebreaking for text configuration file format</title>
      <link>https://community.splunk.com/t5/Splunk-Search/linebreaking-for-text-configuration-file-format/m-p/41069#M9503</link>
      <description>&lt;P&gt;Alright. Thanks alot MarioM. I'll create a new question and hopefully someone has a solution.&lt;/P&gt;</description>
      <pubDate>Wed, 02 May 2012 07:54:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/linebreaking-for-text-configuration-file-format/m-p/41069#M9503</guid>
      <dc:creator>JeffTanYH</dc:creator>
      <dc:date>2012-05-02T07:54:16Z</dc:date>
    </item>
  </channel>
</rss>

