A trace is a set of conditions (subdivided into scope and content) which, when met, cause trace data to be forwarded to IDIH.
The DSR plays the role of determining which messages should be captured, based on trace criteria that are created and activated by the user. The trace criteria identifies the "scope" as well as the "content".
- "Scope" refers to the non-protocol-related elements (such as connections or peers) that are used to select messages for trace content evaluation.
- "Content" refers to the protocol-related elements (such as command codes, AVPs, etc.) that are used to refine the trace criteria.
As request and answer messages are processed by the DSR, they are analyzed for matching any of the active trace definitions, and if so, transfer message components along with supplemental information to the IDIH called trace data. The IDIH can assemble the trace data, and present it to the user leveraging graphical visualization interfaces for additional filtering and analysis.
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, the DSR will suspend trace forwarding until the condition clears, at which time, trace forwarding will resume.
Note: Trace data lost during the time of congestion will not be recovered.