Call Tracing: Using calltrace.sh to Parse the Logs - Revision history

Cchetty: /* Using calltrace.sh to Parse the Logs */

2010-09-14T20:44:06Z

Using calltrace.sh to Parse the Logs

← Older revision		Revision as of 20:44, 14 September 2010
Line 70:		Line 70:

	[[Category:Unified Expert Advisor, Release 7.6(1)]]		[[Category:Unified Expert Advisor, Release 7.6(1)]]
-	~~[[Category:Unified Expert Advisor, Release 8.0]]~~

Cchetty: 1 revision

2010-09-14T20:42:55Z

1 revision

← Older revision

Revision as of 20:42, 14 September 2010

Cchetty: /* Using calltrace.sh to Parse the Logs */

2010-09-14T20:29:52Z

Using calltrace.sh to Parse the Logs

← Older revision		Revision as of 20:29, 14 September 2010
Line 1:		Line 1:
-	~~{{Template:Required Metadata}}~~
	== Using calltrace.sh to Parse the Logs ==		== Using calltrace.sh to Parse the Logs ==

Line 32:		Line 31:
	zgrep $1 MMCA-runtime* > $1.txt		zgrep $1 MMCA-runtime* > $1.txt

-	#Find all interaction ids over previously grepped logs by getting 10th param on	+	#Find all interaction ids over previously grepped logs by \
-	SEND_NEW_INTERACTION_REQ lines	+	getting 10th param on SEND_NEW_INTERACTION_REQ lines
-	GET_INTERACTION_IDS=$(grep SEND_NEW_INTERACTION_REQ $1.txt \| cut -f10 -d'[' \| cut -f1 -d']' \| cut -f2 -d '=')	+	GET_INTERACTION_IDS=$(grep SEND_NEW_INTERACTION_REQ $1.txt \| \
		+	cut -f10 -d'[' \| cut -f1 -d']' \| cut -f2 -d '=')

	#get Contact id from guid log on CONTACT_CREATED line		#get Contact id from guid log on CONTACT_CREATED line
-	CONTACT_ID=$(grep CM-6-CONTACT_CREATED $1.txt \| cut -f2 -d'[' \| cut -f1 -d']' \| cut -f2 -d '=')	+	CONTACT_ID=$(grep CM-6-CONTACT_CREATED $1.txt \| cut -f2 -d'[' \| \
		+	cut -f1 -d']' \| cut -f2 -d '=')

-	#Use array to iterate over any interactions created for this guid, usually there are 2, but there may be 1 or more than 2	+	#Use array to iterate over any interactions created for this
		+	guid, usually there are 2, but there may be 1 or more than 2
	declare -a MPI_INTERACTION_ID		declare -a MPI_INTERACTION_ID
	MPI_INTERACTION_ID=($GET_INTERACTION_IDS)		MPI_INTERACTION_ID=($GET_INTERACTION_IDS)
Line 54:		Line 56:
	done		done

-	#use search strings in file to get all details of call trace and output to fulltrace file	+	#use search strings in file to get all details of call trace
-	zfgrep -h -f $1.fgrepsearch.txt MMCA-runtime* > $1.fulltrace.txt </pre>	+	and output to fulltrace file:
		+	zfgrep -h -f $1.fgrepsearch.txt MMCA-runtime* > \
		+	$1.fulltrace.txt </pre>
	\|-		\|-
	! '''Release'''		! '''Release'''
-	\| Release 7.6(1)	+	\| Release 7.6(1) and Release 8.0(1)
	\|-		\|-
	! '''Associated CDETS #'''		! '''Associated CDETS #'''
Line 66:		Line 70:

	[[Category:Unified Expert Advisor, Release 7.6(1)]]		[[Category:Unified Expert Advisor, Release 7.6(1)]]
		+	[[Category:Unified Expert Advisor, Release 8.0]]

Docwikibot: Bot: Adding {{Template:Required Metadata}}

2009-12-18T19:22:50Z

Bot: Adding {{Template:Required Metadata}}

← Older revision		Revision as of 19:22, 18 December 2009
Line 1:		Line 1:
		+	{{Template:Required Metadata}}
	== Using calltrace.sh to Parse the Logs ==		== Using calltrace.sh to Parse the Logs ==

Cchetty: 1 revision

2009-06-10T22:11:17Z

1 revision

← Older revision

Revision as of 22:11, 10 June 2009

Cchetty: /* Using calltrace.sh to Parse the Logs */

2009-06-09T17:53:51Z

Using calltrace.sh to Parse the Logs

New page

== Using calltrace.sh to Parse the Logs ==

{| border="1"
|-
! '''Problem Summary'''
| You know the Call GUID and you need to trace one call.
|-
! '''Error Message'''
| None.
|-
! '''Possible Cause'''
| Use the following shell script to quickly parse the logs and trace the required call.
|-
! '''Recommended Action'''
| Obtain the logs and use the following bash shell script to grab the important lines from the runtime logs.
To run the script
:# Copy the log files to a computer that can run the script. The computer must be able to run a bash script.
:# Change your working directory to the location of the logs.
:# Run <location of script>/calltrach.sh <guid>
Three files are created:
:* <guid>.txt displays the lines with the guid in them
:* <guid>.fgrep.txt displays the strings used to search with, guid, contactid, mpi interaction ids
:* <guid>.fulltrace.txt contains the complete call trace with any of the above strings in them
{{note|This script can take a long time to run based on the size of the logs. It will search overzipped logs and has to traverse the entire set of logs twice, the first to get the right parameters,the second to get the full call trace. For example, with 5GB of zipped logs (close to 50GBunzipped), on a powerful server, this took approximately 10-15 minutes to complete.}}

<pre>calltrace.sh
------------
#!/bin/bash

#Do full grep over all logs for this GUID provided
zgrep $1 MMCA-runtime* > $1.txt

#Find all interaction ids over previously grepped logs by getting 10th param on
SEND_NEW_INTERACTION_REQ lines
GET_INTERACTION_IDS=$(grep SEND_NEW_INTERACTION_REQ $1.txt | cut -f10 -d'[' | cut -f1 -d']' | cut -f2 -d '=')

#get Contact id from guid log on CONTACT_CREATED line
CONTACT_ID=$(grep CM-6-CONTACT_CREATED $1.txt | cut -f2 -d'[' | cut -f1 -d']' | cut -f2 -d '=')

#Use array to iterate over any interactions created for this guid, usually there are 2, but there may be 1 or more than 2
declare -a MPI_INTERACTION_ID
MPI_INTERACTION_ID=($GET_INTERACTION_IDS)

echo "Contact ID = $CONTACT_ID"

#Echo search strings to new file
echo $CONTACT_ID > $1.fgrepsearch.txt
echo $1 >> $1.fgrepsearch.txt

for interaction in "${MPI_INTERACTION_ID[@]}" ; do
echo "found interaction $interaction"
echo $interaction >> $1.fgrepsearch.txt
done

#use search strings in file to get all details of call trace and output to fulltrace file
zfgrep -h -f $1.fgrepsearch.txt MMCA-runtime* > $1.fulltrace.txt </pre>
|-
! '''Release'''
| Release 7.6(1)
|-
! '''Associated CDETS #'''
| None.
|-
|}

[[Category:Unified Expert Advisor, Release 7.6(1)]]