Getting Data In

Need help in parsing

tmuthuk
Path Finder

Need help in parsing the below data :

000008360.46880570[4940] +++<  15:32:12.832  0h [RC2:0h Owner:0]  Pid/Tid:4940/5196
000008370.46880570[4940]    Source: Routine CReprintServer::initialize(), SubRoutine:<none>, Line:150
000008380.46880570[4940]
000008390.47006419[4940] +++T  15:32:12.832  102h [RC2:0h Owner:0]  Pid/Tid:4940/5196
000008400.47006419[4940]    Source: Routine MANH_Print_Service::PRINT_TEST::GetLabelSubsForCarton, SubRoutine:<none>, Line:0
000008410.47006419[4940]    Substitution Value [0]:  In Catch Block prior call to get substitution m_xmlSession :<session id="NOCORBA"><user>TKMAX93UI</user><role></role><warehouse id="1">873</warehouse><company id="1">01</company><division id="1">01</division><requestor>806_IS01</requestor><menuid>2190</menuid><customerid></customerid><corbalogin>IOR:012020201300000049444c3a506b4c6f67696e5f49463a312e300020010000000000000068000000010102200c00000031302e322e34312e31303500c6eb20201c00000000564201000000022f002020000000033362642051b64c57000cf81c020000000353495605000000010407010320202001000000140000000120202001000100000000000901010000000000</corbalogin><language>ENG</language><browsertype></browsertype><debuglevel></debuglevel><ipaddress></ipaddress><requestid></requestid><pagesize>200</pagesize><dbtype></dbtype><datemask>MM/DD/YY</datemask><timemask>HH:MM</timemask><whse_tz>US/Eastern</whse_tz><user_tz>Warehouse</user_tz><errors/><three_pl enterprise="N" loginsvr3pl="N"><default_co_div id="1" co="01" div="01" skumask=" | | |AAAAAAAA| | | | | "/><eligible_co_div><eligible id="1" co="01" div="01" skumask=" | | |AAAAAAAA| | | | | "/></eligible_co_div></three_pl><print_source>PkMSLaunch</print_source><info><system><logrecords><logrecord index="0"><id>{FE77421B-D2D5-11E2-9470-00505687047E}</id><whenoccurred>2013/06/11 15:32:12.472</whenoccurred><routinename>PkMSError::Error()</routinename><subroutinename>CReprintServer::getShippingLabelSubs()</subroutinename><linenumber>207</linenumber><primaryrc>16908321</primaryrc><severity>64</severity><secondaryrc>0</secondaryrc><secondaryowner>0</secondaryowner><flags>4097</flags><threadid>5196</threadid><procesid>4940</procesid><machineid>KSMS1453</machineid><com><activityid/><contextid/><transactionid/></com><substitutionvalues><substitutionvalue index="0">26002</substitutionvalue><substitutionvalue index="1"></substitutionvalue><substitutionvalue index="2">CReprintServer::getShippingLabelSubs()</substitutionvalue><substitutionvalue index="3"></substitutionvalue><substitutionvalue index="4">ReprintServer has not been initialized!</substitutionvalue><substitutionvalue index="5">0</substitutionvalue></substitutionvalues><text><raw><normal/><short/><long/></raw><expanded><normal/><short/><long/></expanded></text></logrecord></logrecords></system></info></session>
000008420.47006419[4940]
000008430.47006419[4940]
000008440.47118703[4940] +++>  15:32:12.832  0h [RC2:0h Owner:0]  Pid/Tid:4940/5196
000008450.47118703[4940]    Source: Routine CReprintServer::getShippingLabelSubs(), SubRoutine:<none>, Line:1495
000008460.47118703[4940]    Substitution Value [0]: cartonNbr = 00000999990537100272
000008470.47118703[4940]    Substitution Value [1]: labelType = FXG
000008480.47118703[4940]

I need to break it when ever i find 00000836 0.46880570 [4940] +++<

Props.conf , i used is

BREAK_ONLY_BEFORE =\w*\s*\w\W\w*\s*[\w*]\s*\W{3}
SHOULD_LINEMERGE = true

But it is not breaking it properly . Please help me parse this data

Tags (3)
0 Karma

kristian_kolb
Ultra Champion

I would suggest using a different approach;

SHOULD_LINEMERGE = false
LINE_BREAKER = ([\r\n]+)\d+\.\d+\[\d+\]\s+\+\+\+\S\s

Which should cut on the newline before a row with '+++' in it

Hope this helps,

K

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Make Your Machine Data AI-Ready in Splunk

Every team is getting ready for AI agents.   Thursday, November 12, 2026  |  11AM  PST / 2PM EST   ...

Splunk Asynchronous Forwarding Explained

Splunk asynchronous forwarding is often misunderstood as simply setting autoLBVolume. That is not quite right. ...

How to Monitor AI Agents with Splunk Agent Observability

Let’s say I’m running a travel planning AI app in production. A user asks for three concise hotel options in ...