The requirements for setting up a system to store alarm history include a separate database definition and calendars and schedules that define when to capture historical data. Profiles are required to define exactly what data are captured.
A database definition establishes the configuration settings and other parameters required to establish a connection between Operations Center and a specific database.
The general steps to store alarm history:
Configure and enable a database definition to connect with your database.
For more information, see Section 7.5, Configuring the Service Warehouse.
Edit time categories as required and create one or more linked calendars and schedules for capturing and storing data.
For more information, see Section 13.0, Time Categories, Calendars, and Schedules.
Set up and activate a profile that contains an Alarm History expression.
The profile and expression determine which specific properties are stored when the profile runs. The profile is linked to a schedule, which determines when the alarm data is captured.
After capturing and storing alarm history, do one of the following to view the alarm history:
View alarm history for elements by using the Historical: Alarms option in the Alarms view.
Change the alarm display using the options listed under the Format menu. These options include defining the maximum number of historical alarms displayed.
Double-click an alarm recorded, then select the History tab to view the history of a single alarm.
To store alarm history, SLA data, or performance data, the element properties created by an adapter must meet the supported schema as specified in the Data Dictionary. Otherwise, a “value too large” error occurs, displaying the maximum allowed length for a property value and the actual length. For example, DNames cannot exceed 3,000 characters.