topic Re: How do I configure line breaking in props.conf for my sample log file? in Getting Data In

How do I configure line breaking in props.conf for my sample log file?

myorkows — Fri, 28 Oct 2016 22:15:43 GMT

Would like the events to be split after ) --[End]--------------------$

 (0x03000000:NameValue)urn:hl7-org:v2xml:Remainder        = NULL$
        )$
      )$
    )$
  )$
)  --[End]--------------------$
--[Start]-------------------  TIME_STAMP: 2016-06-16 09:01:52.757998 --  MESSAGE_ID: 'Unknown' --  Flow: 'Messages_Received_From_CHCS_Or_TMDGReceiver' --  Milestone: 'From Ack' --  Message:  ( ['GENERICROOT' : 0x7effe100e650]$
  (0x01000000:Name):Properties = ( ['MQPROPERTYPARSER' : 0x7effe104c9d0]$
    (0x03000000:NameValue):MessageSet             = NULL$
    (0x03000000:NameValue):MessageType            = NULL$
    (0x03000000:NameValue):MessageFormat          = NULL$
    (0x03000000:NameValue):Encoding               = NULL$
    (0x03000000:NameValue):CodedCharSetId         = NULL$

Re: How do I configure line breaking in props.conf for my sample log file?

skoelpin — Fri, 28 Oct 2016 23:26:33 GMT

Add this

[Your_SourceType]
TIME_PREFIX = ^
TIME_FORMAT = %Y-%m-%d %H:%M:%S,$3N
BREAK_ONLY_BEFORE = --\[Start]\S+

Restart your Splunk indexer SPLUNK_HOME/bin/splunk restart

Re: How do I configure line breaking in props.conf for my sample log file?

myorkows — Tue, 29 Sep 2020 11:37:56 GMT

Thanks for your quick response...this is what the events look like now after adding your changes to the props.conf.

11/1/16
12:03:19.502 AM
) -- ExceptionList: --[End]--------------------
--[Start]------------------- TIME_STAMP: 2016-11-01 00:03:19.502293 -- MESSAGE_ID: NULL -- Flow: 'crdOrdLrUpdate_FLOW' -- Milestone: 'Lab/Rad Stored Proc Success' -- Message: ( 'MQROOT' : 0x7f4524788780:Properties = ( 'MQPROPERTYPARSER' : 0x7f45248ecaa0:MessageSet = NULL
(0x03000000:NameValue):MessageType = NULL
(0x03000000:NameValue):MessageFormat = NULL
(0x03000000:NameValue):Encoding = NULL
(0x03000000:NameValue):CodedCharSetId = NULL
(0x03000000:NameValue):Transactional = NULL
(0x03000000:NameValue):Persistence = NULL
(0x03000000:NameValue):CreationTime = NULL
(0x03000000:NameValue):ExpirationTime = NULL
(0x03000000:NameValue):Priority = NULL
(0x03000000:NameValue):ReplyIdentifier = NULL
(0x03000000:NameValue):ReplyProtocol = 'MQ' (CHARACTER)
(0x03000000:NameValue):Topic = NULL
(0x03000000:NameValue):ContentType = NULL
(0x03000000:NameValue):IdentitySourceType = NULL
(0x03000000:NameValue):IdentitySourceToken = NULL
(0x03000000:NameValue):IdentitySourcePassword = NULL
(0x03000000:NameValue):IdentitySourceIssuedBy = NULL
(0x03000000:NameValue):IdentityMappedType = NULL
(0x03000000:NameValue):IdentityMappedToken = NULL
(0x03000000:NameValue):IdentityMappedPassword = NULL
(0x03000000:NameValue):IdentityMappedIssuedBy = NULL
)

Collapse
host = dev2iib1 source = /iibshare/logs/DHA_ESB_NODE_1/Tuesday.log sourcetype = iib

---I would like the events to look like this

--[Start]------------------- TIME_STAMP: 2016-11-01 00:03:19.502293 -- MESSAGE_ID: NULL -- Flow: 'crdOrdLrUpdate_FLOW
1 stuff
2 stuff
3 stuff
ExceptionList: --[End]--------------

Thanks so much for all your help!

Re: How do I configure line breaking in props.conf for my sample log file?

skoelpin — Tue, 01 Nov 2016 14:56:06 GMT

Whoops. I edited my answer to the correct configuration, try pasting the updated answer into your props.conf and restart.. This should work

Re: How do I configure line breaking in props.conf for my sample log file?

myorkows — Tue, 01 Nov 2016 18:41:50 GMT

THANKS!!!...that worked!

Re: How do I configure line breaking in props.conf for my sample log file?

myorkows — Tue, 01 Nov 2016 18:45:52 GMT

Sorry I can't award any points...must be too new.

Re: How do I configure line breaking in props.conf for my sample log file?

skoelpin — Tue, 01 Nov 2016 18:46:50 GMT

That's ok, you could upvote the answer which gives me points if you feel like its worth it

Re: How do I configure line breaking in props.conf for my sample log file?

myorkows — Tue, 01 Nov 2016 18:50:16 GMT

Okay...just did ...Thanks again!