20022010 Ericsson AB. All Rights Reserved. The contents of this file are subject to the Erlang Public License, Version 1.1, (the "License"); you may not use this file except in compliance with the License. You should have received a copy of the Erlang Public License along with this software. If not, it can be retrieved online at http://www.erlang.org/. Software distributed under the License is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License for the specific language governing rights and limitations under the License. Advanced examples Håkan Mattsson Håkan Mattsson Håkan Mattsson %VSN% et_examples.xml
A simulated Mnesia transaction

The Erlang code for running the simulated Mnesia transaction example in the previous chapter is included in the et/examples/et_demo.erl file:

If you invoke the et_demo:sim_trans() function, a Viewer window will pop up and the sequence trace will be almost the same as if the following Mnesia transaction would have been run:

mnesia:write({my_tab, key, val}) end).]]>

And the viewer window will look like:

{ok, Viewer} = et_viewer:start([]). {ok,<0.40.0>;} 2> et_demo:sim_trans(). {ok,{table_handle,<0.45.0>,24596,trace_ts, #Fun}}]]>

A simulated Mnesia transaction which writes one record
Some convenient functions used in the <c>Mnesia</c> transaction example

The module_as_actor filter converts the Event Records so the module names becomes actors and the invoked functions becomes labels. If the information about who the caller was it will be displayed as an arrow directed from the caller to the callee. The [{message, {caller}}, {return_trace}] options to dbg:tpl/2 function will imply the necessary information in the Erlang traces. Here follows the module_as_actor filter:

The plain_process_info filter does not alter the Event Records. It merely ensures that the event not related to processes are skipped:

The plain_process_info_nolink filter does not alter the Event Records. It do makes use of the plain_process_info , but do also ensure that the process info related to linking and unlinking is skipped:

In order to simplify the startup of an et_viewer process with the filters mentioned above, plus some others (that also are found in et/examples/et_demo.erl src/et_collector.erl the et_demo:start/0,1 functions can be used:

A simple one-liner starts the tool:

The filters are included by the following parameters:

Erlang trace of a real Mnesia transaction

The following piece of code et_demo:trace_mnesia/0 activates call tracing of both local and external function calls for all modules in the Mnesia application. The call traces are configured cover all processes (both existing and those that are spawned in the future) and include timestamps for trace data. It do also activate tracing of process related events for Mnesia's static processes plus the calling process (that is your shell). Please, observe that the whereis/1 call in the following code requires that both the traced Mnesia application and the et_viewer is running on the same node:

The et_demo:live_trans/0 function starts the global Collector, starts a Viewer, starts Mnesia, creates a local table, activates tracing (as described above) and registers the shell process is as 'my_shell' for clarity. Finally a simple Mnesia transaction that writes a single record is run:

Now we run the et_demo:live_trans/0 function:

et_demo:live_trans(). {atomic,ok}]]>

Please, explore the different filters in order to see how the traced transaction can be seen from different point of views:

A real Mnesia transaction which writes one record
Erlang trace of Megaco startup

The Event Tracer (ET) tool was initially written in order to demonstrate how messages where sent over the Megaco protocol. This were back in the old days before the standard bodies of IETF and ITU had approved Megaco (also called H.248) as an international standard.

In the Megaco application of Erlang/OTP, the code is carefully instrumented with calls to et:trace_me/5. For each call a detail level is given in order to enable dynamic control of the trace level in a simple manner.

The megaco_filter module implements a customized filter for Megaco messages. It does also make use of trace_global combined with usage of the trace_pattern:

Options = [{event_order, event_ts}, {scale, 3}, {max_actors, infinity}, {trace_pattern, {megaco, max}}, {trace_global, true}, {dict_insert, {filter, megaco_filter}, fun filter/1}, {active_filter, megaco_filter}, {title, "Megaco tracer - Erlang/OTP"}], et_viewer:start(Options).]]>

First we start an Erlang node with a global Collector and its Viewer.

megaco_filter:start(). {ok,<0.48.0>}]]>

Secondly we start another Erlang node which we connect the observer node, before we start the application that we want to trace. In this case we start a Media Gateway Controller that listens for both TCP and UDP on the text and binary ports for Megaco:

net:ping(observer@falco). pong (mgc@falco)2> megaco:start(). ok (mgc@falco)3> megaco_simple_mgc:start(). {ok,[{ok,2944, {megaco_receive_handle,{deviceName,"controller"}, megaco_pretty_text_encoder,[],megaco_tcp,dynamic}}, {ok,2944, {megaco_receive_handle,{deviceName,"controller"}, megaco_pretty_text_encoder,[],megaco_udp,dynamic}}, {ok,2945, {megaco_receive_handle,{deviceName,"controller"}, megaco_binary_encoder,[],megaco_tcp,dynamic}}, {ok,2945, {megaco_receive_handle,{deviceName,"controller"}, megaco_binary_encoder,[],megaco_udp,dynamic}}]}]]>

And finally we start an Erlang node for the Media Gateways and connect to the observer node. Each Media Gateway connects to the controller and sends an initial Service Change message. The controller accepts the gateways and sends a reply to each one using the same transport mechanism and message encoding according to the preference of each gateway. That is all combinations of TCP/IP transport, UDP/IP transport, text encoding and ASN.1 BER encoding:

net:ping(observer@falco). pong (mg@falco)2> megaco_simple_mg:start(). [{{deviceName,"gateway_tt"}, {error,{start_user,megaco_not_started}}}, {{deviceName,"gateway_tb"}, {error,{start_user,megaco_not_started}}}, {{deviceName,"gateway_ut"}, {error,{start_user,megaco_not_started}}}, {{deviceName,"gateway_ub"}, {error,{start_user,megaco_not_started}}}] (mg@falco)3> megaco:start(). ok (mg@falco)4> megaco_simple_mg:start(). [{{deviceName,"gateway_tt"}, {1, {ok,[{'ActionReply',0,asn1_NOVALUE,asn1_NOVALUE, [{serviceChangeReply, {'ServiceChangeReply', [{megaco_term_id,false,["root"]}], {serviceChangeResParms, {'ServiceChangeResParm', {deviceName,"controller"}, asn1_NOVALUE,asn1_NOVALUE,asn1_NOVALUE, asn1_NOVALUE}}}}]}]}}}, {{deviceName,"gateway_tb"}, {1, {ok,[{'ActionReply',0,asn1_NOVALUE,asn1_NOVALUE, [{serviceChangeReply, {'ServiceChangeReply', [{megaco_term_id,false,["root"]}], {serviceChangeResParms, {'ServiceChangeResParm', {deviceName,"controller"}, asn1_NOVALUE,asn1_NOVALUE,asn1_NOVALUE, asn1_NOVALUE}}}}]}]}}}, {{deviceName,"gateway_ut"}, {1, {ok,[{'ActionReply',0,asn1_NOVALUE,asn1_NOVALUE, [{serviceChangeReply, {'ServiceChangeReply', [{megaco_term_id,false,["root"]}], {serviceChangeResParms, {'ServiceChangeResParm', {deviceName,"controller"}, asn1_NOVALUE,asn1_NOVALUE,asn1_NOVALUE, asn1_NOVALUE}}}}]}]}}}, {{deviceName,"gateway_ub"}, {1, {ok,[{'ActionReply',0,asn1_NOVALUE,asn1_NOVALUE, [{serviceChangeReply, {'ServiceChangeReply', [{megaco_term_id,false,["root"]}], {serviceChangeResParms, {'ServiceChangeResParm', {deviceName,"controller"}, asn1_NOVALUE,asn1_NOVALUE, asn1_NOVALUE,...}}}}]}]}}}]]]>

The Megaco adopted viewer looks like this, when we have clicked on the [gateway_tt] actor name in order to only display the events regarding that actor:

The viewer adopted for Megaco

A pretty printed Megaco message looks like this:

A textual Megaco message

And the corresponding internal form for the same Megaco message looks like this:

The internal form of a Megaco message