2.2 Trace Overview

A trace is a set of conditions (subdivided into scope and content) which, when met, cause trace data to be forwarded to IDIH.

A DSR DA-MP plays the role of determining which messages should be captured based on trace criteria created and activated by the user. The trace criteria identifies the scope and content.

• Scope refers to the non-protocol-related elements (such as connections or peers) used to select messages for trace content evaluation.
• Content refers to the protocol-related elements (such as command codes and AVPs) used to refine the trace criteria.

As DSR processes request and answer messages, they are analyzed for matching any of the active trace definitions. If a match is found, message components along with supplemental information, called trace data, are transferred to the IDIH. The IDIH assembles the trace data and presents it to the user leveraging graphical visualization interfaces for additional filtering and analysis.

Figure 2-1 IDIH Trace Overview

IDIH does not guarantee a fixed number of days of data storage. Storage life is based on disk space. Some of the factors impacting storage life are trace parameters (very inclusive or very discriminatory) and record size.

During congestion, DSR suspends trace forwarding until the condition clears, at which time, trace forwarding resumes.

Note:

Trace data lost during the time of congestion is not recovered.