~ubuntu-branches/debian/squeeze/erlang/squeeze

Implements an off-line logfile merger, merging binary trace-log files from several nodes together in chronological order. The logfile merger can also do pid-to-alias translations.

The logfile merger is supposed to be called from the Erlang shell or a higher layer trace tool. For it to work, all logfiles and trace information files (containing the pid-alias associations) must be located in the file system accessible from this node and organized according to the API description.

The logfile merger starts a process, the output process, which in its turn starts one reader process for every node it shall merge logfiles from. Note that the reason for a process for each node is not remote communication, the logfile merger is an off-line utility, it is to sort the logfile entries in chronological order.

The logfile merger can be customized both when it comes to the implementation of the reader processes and the output the output process shall generate for every logfile entry.

</description>

<funcs>

<func>

<name>merge(Files, OutFile) -></name>

<name>merge(Files, WorkHFun, InitHandlerData) -></name>

<name>merge(Files, BeginHFun, WorkHFun, EndHFun, InitHandlerData)

-> {ok, Count} | {error, Reason}</name>

<fsummary>Merge logfiles into one file in chronological order

</fsummary>

<type>

<v>Files = [FileDescription]</v>

<v> FileDescription = FileSet | {reader,RMod,RFunc,FileSet}

</v>

<v>  FileSet = {Node, LogFiles}</v>

<v>   LogFiles =

[{trace_log, [FileName]} | {ti_log, [FileName]}]</v>

<v>    FileName = string()</v>

<v>  RMod = RFunc = atom()</v>

<v>OutFile = string()</v>

<v>BeginHFun = fun(InitHandlerData) ->

{ok, NewHandlerData} | {error, Reason}</v>

<v>WorkHFun = fun(Node, LogEntry, PidMappings, HandlerData) ->

{ok, NewHandlerData}</v>

<v> LogEntry = tuple()</v>

<v> PidMappings = term()</v>

<v>EndHFun = fun(HandlerData) -> ok | {error, Reason}</v>

<v>Count = int()</v>

<v>Reason = term()</v>

</type>

<desc>

Merges the logfiles in <c>Files</c> together into one file in chronological order. The logfile merger consists of an output process and one or several reader processes.

Returns <c>{ok, Count}</c> where <c>Count</c> is the total number of log entries process, if successful.

When specifying <c>LogFiles</c>, currently the standard reader-process only supports:

<list>

<item>one single file</item>

<item>a list of wraplog files, following the naming convention <c><Prefix><Nr><Suffix></c>.</item>

</list>

<c>FileDescription == {reader,RMod,RFunc,FileSet}</c> indicates that <c>spawn(RMod, RFunc, [OutputPid,LogFiles])</c> shall create a reader process.

The output process is customized with <c>BeginHFun</c>, <c>WorkHFun</c> and <c>EndHFun</c>. If using <c>merge/2</c> a default output process configuration is used, basically creating a text file and writing the output line by line. <c>BeginHFun</c> is called once before requesting log entries from the reader processes. <c>WorkHFun</c> is called for every log entry (trace message) <c>LogEntry</c>. Here the log entry typically gets written to the output. <c>PidMappings</c> is the translations produced by the reader process. <c>EndHFun</c> is called when all reader processes have terminated.

The standard reader process is implemented in the module <c>inviso_lfm_tpreader</c> (trace port reader). It understands Erlang linked in trace-port driver generated trace-logs and <c>inviso_rt_meta</c> generated trace information files.

</desc>

</func>

</funcs>

<title>Writing Your Own Reader Process</title>

Writing a reader process is not that difficult. It must:

<list>

<item>Export an init-like function accepting two arguments, pid of the output process and the <c>LogFiles</c> component. <c>LogFiles</c> is actually only used by the reader processes, making it possible to redefine <c>LogFiles</c> if implementing an own reader process.</item>

<item>Respond to <c>{get_next_entry, OutputPid}</c> messages with <c>{next_entry, self(), PidMappings, NowTimeStamp, Term}</c> or <c>{next_entry, self(), {error,Reason}}</c>.</item>

<item>Terminate normally when no more log entries are available.</item>

<item>Terminate on an incoming EXIT-signal from <c>OutputPid</c>.</item>

</list>

The reader process must of course understand the format of a logfile written by the runtime component.

</section>

<aname>Lennart Öhman</aname>

<email>support@erlang.ericsson.se</email>

</authors>

</erlref>

b'\\ No newline at end of file'

Older »