At the first scheduled interval after all Time Management and Data Warehouse objects are set up and configured, the BSLM Scheduling Engine fires an event for BSLM expressions. This causes the engine to poll the matched elements for the specific performance data, then store them to the database tables, as described in Table 1-1.
Table 1-1 Data Warehouse Performance Database Tables
|
Database Table |
Description |
|
|---|---|---|
|
BSATimeBand |
If the current time normalized to a five-second interval falls within an existing BSATimeBand record, the existing time band information is used. If not, then a new BSATimeBand record is created for the current performance event. The new/existing time band record is cached by the BSLM Engine to reduce database overhead for future events. |
|
|
BSASeries |
The BSASeries table is queried to determine if a series record exists for the current Profile/Subject/Expression combination. For example: |
|
|
Profile Subject Expression |
Test 1 Profile TEC (that is, the Tec element above) Element Conditions |
|
|
If a series record already exists, the existing series record is used to populate the foreign keys in the BSAFactSeriesData record. If the series information does not exist, a new record is inserted and foreign keys populated as required. The new/existing BSASeries record is cached by the BSLM Engine to minimize database overhead. |
||
|
BSAFactSeriesData |
This table stores the actual performance data points retrieved by the BSLM Engine. The exception to this rule is the Alarm Field expression. Since alarms are inspected when the event is received by the Operations Center server, the specific alarm field is stored when processed. |
|
|
RootCauseTables:
|
If the expression (such as. ElementConditionChange) requires persistence of the root cause information. |
|