5.2 Performance Reports

Historical performance data, such as element properties, alarm properties, performance series data, and severity counts can be captured in Operations Center and is then available in SQL Views in the Performance table.

A BSLM license key is required for performance reporting.

To capture performance data, you must set up element profiles, which apply matching criteria to select elements for which to collect data, and expressions, which identify the type of data saved for these elements. For more information about profiles and expressions, see Capturing Alarm and Performance History in the Operations Center Server Configuration Guide.

In addition to collecting performance data for elements residing on the local Operations Center server, performance data for elements on remote servers can also be collected. To access data from another server requires an Intercommunication adapter. Data related to the Service Level Manager (such as availability, downtime, SLA/objective health, and SLA/objective key metrics) is not available over an Intercommunication adapter. For more information on the Intercommunication adapter, see the Operations Center Adapter and Integration Guide.

You can create a report using SQL Views that contains performance data from both the local Operations Center server and remote Operations Center servers.

There are no system views that use the Performance table. So to create a report using performance data, you must create a custom view then use that view in your reporting tool.

To create a performance report for local and remote data:

  1. Create an InterCommunication adapter.

    For instructions, see the Operations Center Adapter and Integration Guide.

  2. Create and start a profile with expressions that track the desired performance data, such as an element property or an alarm property.

    For example, create a profile that stores the total number of alarms in the Operations Center server element or stores the queue size of the Data Warehouse element.

  3. Create a view.

    In creating this view, select an element that has profile information, then select Performance as the table.

  4. Configure SQL Views, if you have not done so already.

    For more information, see Section 2.1, Prerequisites.

  5. Extract the performance data into Microsoft Excel or Crystal Reports and create a report.

    For more information, see Section 3.0, Queries and Reports.