1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
|
-
+
-
+
|
<h1>Logprocessor</h1>
<h2>Purpose</h2>
<h3>Purpose</h3>
With logpro you can write command files to rigorously analzye log files. For example you may have a complex simulation with many steps, compilation, simulation, analysis, clean up etc. You want to know in an automated way if the simulation ran. Manually reading the log file(s) once or twice seaching for errors, warnings and messages is fine but by the third or forth time you want to automate it. Logpro can help.
Running logpro. EXAMPLE: Run the program "runsim" passing the output through logpro using the cmdfile.logpro log analysis command file. The anotated log file is written to "run.html" and run-logro.log.
<verbatim>
% runsim | logpro cmdfile.logpro run.html > run-logpro.log
</verbatim>
<h2>Command file details</h2>
<h3>Command file details</h3>
Your command file is written in scheme but don't let that scare you. Only a handful of single line stanzas are needed to write a rock solid log analyzer. Here is an [example command file] and the [logpro output] from running against this [example log file]
<h3>Syntax</h3>
<verbatim>
( trigger "trigger name" #/trigger pattern/ )
( section "start trigger" "end trigger" )
( expect [in|not-in] "section name" [> or < or =] integer #/regular expression/ )
|