Parsing Tuxedo Logs

Special Forums UNIX and Linux Applications Parsing Tuxedo Logs

10-16-2009

Registered User

7, 0

Join Date: Feb 2009

Last Activity: 24 September 2010, 6:38 PM EDT

Posts: 7

Thanks Given: 0

Thanked 0 Times in 0 Posts

Parsing Tuxedo Logs

Right now I am parsing Tuxedo logs to calculate response times for various services. I was hoping to find a log tool that had support for Tuxedo and would generate drill down html reports.

---------- Post updated at 02:35 PM ---------- Previous update was at 02:33 PM ----------

I just wanted to add that I have found one tool that is pretty nice but it only runs interactively in MS Windows. And doesn't have the ability to print or export it's results.

Tuxedo Performance Analyzer

Lurch

View Public Profile for Lurch

Find all posts by Lurch

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Infrastructure Monitoring

Tuxedo server monitoring

Hi I like to use tmadmin commands to monitor running application in tuxedo server 12c.But When i use tmadmin help command i get only meta commands.But i like to check printconn,printclient,printserver like that.But these commands are not avaialble in list.I here pasted the help command...

2. Infrastructure Monitoring

Tuxedo Query

Hi , The tuxedo is installed in solaris server. I would like to grab one particular tuxedo service from solaris command line. Note: I would like to grab only for service related line. Thank & Regards, Mani

3. UNIX and Linux Applications

tuxedo information

Hi, Anyone know about tuxedo middleware tool. If you aware please guild me. 1) where will i get information about it ? 2) What kind of the basis issue ? I am new in tuxedo, I would like to aware before start my job. Thanks & Regards, Mani

4. Shell Programming and Scripting

Please help on tuxedo linking problem

Dear Unixians, I have try to link my libraries with tuxedo that showing following errors, ] My make file few lines: .... actual linking Please help on this. Thanks,KKL.

5. Shell Programming and Scripting

Help parsing logs maybe with menu and variables?

I would like to parse through some logs looking for things like exception or failed (grep -i failed). Ideal would be if it were in a menu format so someone without unix ability could just choose option 1 2 or 3 etc. If I could pass the hostname to a variable also that would be awesome, so someone...

6. Shell Programming and Scripting

Parsing log files, displaying logs between specific dates

Sorry, couldn't really think of a simple subject/title. So, I have a log file, and the dates are displayed like so: 2009-03-05 02:49:44 So the first and second field are the date/time. I can change them into a unix timestamp easily with: date -d "2009-03-05 02:49:44" +%s However,...

7. Shell Programming and Scripting

Parsing out the logs and generating report

My file will contain following(log.txt): start testcase: config loading ...... error XXXX ..... end testcase: config loading, result failed start testcase: ping check ..... error ZZZZZ ..... error AAAAA end testcase: Ping check, result failed I am expecting below output. ...

8. UNIX for Dummies Questions & Answers

Parsing Powerbroker Logs for SysAdmin Changes (SOX)

I need to identify a list of AIX command strings that can be used to parse Powerbroker logs for changes that are being made by Unix SysAdmins. Need to filter out (as much as possible) inquiry or routine maintenance activity and concentrate on software/security changes. This is for internal...

9. UNIX for Dummies Questions & Answers

Tuxedo for MQ???

Hi, I am new to the UNIX environment so putting this query here. Was working with mainframes till now. The UNIX system i am working on uses MQ series along with Tuxedo for communicating with mainframes. I want to know why is Tuxedo required in order to use MQ on the unix side? On mainframes...

LEARN ABOUT DEBIAN

trimhistory

TRIMHISTORY(8)						      System Manager's Manual						    TRIMHISTORY(8)

NAME

       trimhistory - Remove old Xymon history-log entries

SYNOPSIS

       trimhistory --cutoff=TIME [options]

DESCRIPTION

       The  trimhistory  tool  is  used  to  purge old entries from the Xymon history logs. These logfiles accumulate information about all status
       changes that have occurred for any given service, host, or the entire Xymon system, and is used to generate the event- and history-log web-
       pages.

       Purging	old  entries  can  be done while Xymon is running, since the tool takes care not to commit updates to a file if it changes mid-way
       through the operation. In that case, the update is aborted and the existing logfile is left untouched.

       Optionally, this tool will also remove logfiles from hosts that are no longer defined in the Xymon bb-hosts(5) file. As an extension,  even
       logfiles from services can be removed, if the service no longer has a valid status-report logged in the current Xymon status.

OPTIONS

       --cutoff=TIME
	      This  defines  the  cutoff-time when processing the history logs. Entries dated before this time are discarded. TIME is specified as
	      the number of seconds since the beginning of the Epoch. This is easily generated by the GNU date(1) utility, e.g. the following com-
	      mand will trim history logs of all entries prior to Oct. 1st 2004:

		  trimhistory --cutoff=`date +%s --date="1 Oct 2004"`

       --outdir=DIRECTORY
	      Normally,  files	in  the  BBHIST  directory  are replaced. This option causes trimhistory to save the shortened history logfiles to
	      another directory, so you can verify that the operation works as intended. The output directory must exist.

       --drop Causes trimhistory to delete files from hosts that are not listed in the bb-hosts(5) file.

       --dropsvcs
	      Causes trimhistory to delete files from services that are not currently tracked  by  Xymon.  Normally  these  files  would  be  left
	      untouched if only the host exists.

       --droplogs
	      Process the BBHISTLOGS directory also, and delete status-logs from events prior to the cut-off time. Note that this can dramatically
	      increase the processing time, since there are often lots and lots of files to process.

       --progress[=N]
	      This will cause trimhistory to output a status line for every N history logs or status-log collections it processes, to indicate how
	      far it has progressed. The default setting for N is 100.

       --env=FILENAME
	      Loads the environment from FILENAME before executing trimhistory.

       --debug
	      Enable debugging output.

FILES

       $BBHIST/allevents
	      The eventlog of all events that have happened in Xymon.

       $BBHIST/HOSTNAME
	      The per-host eventlogs.

       $BBHIST/HOSTNAME.SERVICE
	      The per-service eventlogs.

       $BBHISTLOGS/*/*
	      The historical status-logs.

ENVIRONMENT VARIABLES

       BBHIST The directory holding all history logs.

       BBHISTLOGS
	      The top-level directory for the historical status-log collections.

       BBHOSTS
	      The location of the bb-hosts file, holding the list of currently known hosts in Xymon.

SEE ALSO

       xymon(7), bb-hosts(5)

Xymon							    Version 4.2.3:  4 Feb 2009						    TRIMHISTORY(8)

UNIX and Linux Applications