et

20022009 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. et Håkan Mattsson Håkan Mattsson Håkan Mattsson %VSN%

et Main API of the Event Trace (ET) application

Interface module for the Event Trace (ET) application

report_event(DetailLevel, FromTo, Label, Contents) -> hopefully_traced report_event(DetailLevel, From, To, Label, Contents) -> hopefully_traced phone_home(DetailLevel, FromTo, Label, Contents) -> hopefully_traced phone_home(DetailLevel, From, To, Label, Contents) -> hopefully_traced Reports an event, such as a message DetailLevel = integer(X) when X =< 0, X >= 100 From = actor() To = actor() FromTo = actor() Label = atom() | string() | term() Contents = [{Key, Value}] | term() actor() = term()

Reports an event, such as a message.

These functions are intended to be invoked at strategic places in user applications in order to enable simplified tracing. The functions are extremely light weight as they do nothing besides returning an atom. These functions are designed for being traced. The global tracing mechanism in et_collector defaults to set its trace pattern to these functions.

The label is intended to provide a brief summary of the event. A simple tag would do.

The contents can be any term but in order to simplify post processing of the traced events, a plain list of {Key, Value} tuples is preferred.

Some events, such as messages, are directed from some actor to another. Other events (termed actions) may be undirected and only have one actor.