Erlang -- et

User's Guide
Reference Manual
Release Notes
PDF
Top

Event Tracer (ET)
Reference Manual
Version 1.4.4.1

Expand All
Contract All

Table of Contents

- et
  - Top of manual page
  - trace_me/5
  - trace_me/4
  - phone_home/4
  - phone_home/5
  - report_event/4
  - report_event/5
- et_collector
  - Top of manual page
  - start_link/1
  - stop/1
  - save_event_file/3
  - load_event_file/2
  - report/2
  - report_event/5
  - report_event/6
  - make_key/2
  - get_table_handle/1
  - get_global_pid/0
  - change_pattern/2
  - dict_insert/3
  - dict_insert/3
  - dict_insert/3
  - dict_lookup/2
  - dict_delete/2
  - dict_match/2
  - multicast/2
  - start_trace_client/3
  - iterate/3
  - iterate/5
  - clear_table/1
- et_selector
  - Top of manual page
  - make_pattern/1
  - change_pattern/1
  - parse_event/2
- et_viewer
  - Top of manual page
  - file/1
  - start/0
  - start/1
  - start_link/1
  - get_collector_pid/1
  - stop/1

# et

### MODULE

et

### MODULE SUMMARY

Main API of the Event Trace (ET) application

### DESCRIPTION

Interface module for the Event Trace (ET) application

### EXPORTS

trace_me(DetailLevel, From, To, Label, Contents) -> hopefully_traced

Types:

DetailLevel = integer(X) when X =< 0, X >= 100
From = actor()
To = actor()
Label = atom() | string() | term()
Contents = [{Key, Value}] | term()
actor() = term()

A function that is intended to be traced.

This function is 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. The 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. It is preferred to use an atom but a string would also 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.

trace_me(DetailLevel, FromTo, Label, Contents) -> hopefully_traced

Invokes et:trace_me/5 with both From and To set to FromTo.

phone_home(DetailLevel, FromTo, Label, Contents) -> hopefully_traced
phone_home(DetailLevel, From, To, Label, Contents) -> hopefully_traced

These functions sends a signal to the outer space and the caller hopes that someone is listening. In other words, they invoke et:trace_me/4 and et:trace_me/5 respectively.

report_event(DetailLevel, FromTo, Label, Contents) -> hopefully_traced
report_event(DetailLevel, From, To, Label, Contents) -> hopefully_traced

Deprecated functions which for the time being are kept for backwards compatibility. Invokes et:trace_me/4 and et:trace_me/5 respectively.