Manager - statistics events processing
The statistics events are worked out starting from protocol events of the
BOP-SL, BOP-DL or Ethernet - 802.3 type.
The generation processing of statistics events carries out filtering,
decoding and counting operation on the protocol events.
The execution of the processing and the recording of the statistics event
file .ASE are launched by:
- the MANAGER during profile execution.
- the FILTER-EXEC statistics applied on protocol event file already
recorded.
The MANAGER launches statistics if the used profile includes the following
specifications:
- statistics event file name.
- its recording mode.
- the file max size.
- statistics filter file name.
If no file is mentioned, the Record specifications of the
default filter \CLATOOLS\ TAC_DFT.ASF are used.
The statistics filter used includes Record specifications:
- a definition of the protocols used on the interfaces.
- the Time Sampling period for the statistics events generation.
- types of counting details to be generated or not for each protocol layer.
Each statistics event contains:
- the used layer.
- the used protocol.
- the used direction.
- the interface number.
- the interface status at the time of generation.
- the absolute date with resolution of 0.1 ms.
- the length of the event.
- the time sampling period with maximum resolution of 1s.
- the DATA-STATISTICS zone.
The DATA-STATISTICS zone includes all the elementary counters (by types of
protocol items) in the form identifier+value+count with:
- identifier: identifier of the elementary counter type.
- value: particular control field value related to the used protocol (Q931
Call reference, X25 LCN).
- count: value of the elementary counter at the end of the time-sampling
period.
The types of elementary counters of the used protocol layer can be:
- counters by protocol event type (or Decoding counters).
- counters by field-value.
- data flow and frames counters (or Measure counters).
The statistics events files .ASE contain in addition other internal
information such as:
- beginning and end of file events.
- beginning and end of profile execution events.
- warning events as (Analysis hole).
- interface status events: (Monitoring On/Off).
|