8.3 Generating Reports on Remote SLA Data

When generating SLA reports in the dashboard, the portal/query engine can make requests that are routed to either local or remote servers in order to report on all relevant SLA data that a user has permissions to access and view.

8.3.1 SLA Metrics

The following SLA metrics are available for remote elements for SLA compliance reports:

  • Agreement and objective availability (not element availability)

  • Agreement and objective downtime (not element downtime)

  • Agreement and objective outages and outage counts (not element outages and outage counts)

  • Agreement and objective health

  • Agreement and objective key metric

  • Agreement and objective breach alarms and breach counts

  • Agreement and objective service level metric alarms

  • Element condition change data

  • Performance metrics (alarm or element properties)

For all Alarms listings, select the following data for elements with remote SLAs:

  • Outages

  • Service Level Breaches (Agreement and Objective)

  • Service Level Metrics (Agreement and Objective)

Similar to SLA reports for local data, all queries for SLA reports support filtering options, such as time intervals, calendars, time categories, warnings, and so on. However, it is not possible to view remote time category names over the InterCommunication connection. Therefore, only the local time category names display. If a remote SLA has a remote calendar definition, the SLA engine calculates the appropriate values based on the remote time categories, but the local portal displays time category names based on the local server definition only.

When creating an SLA report, both the local and remote agreements and objectives display in the portal selection list. The remote agreements begin with the word “Remote.”

8.3.2 Troubleshooting Remote SLA Data Access Problems

If you experience problems accessing remote SLA data, the following common reasons might prevent viewing all remote SLAs for a remote element:

  • Check box not selected: Open the remote element’s Service Level Agreements property page. In the SLA’s Objectives tab, the Allow Agreement to Be Visible Remotely check box should be selected.

  • Missing permissions: Verify the InterCommunication adapter user has appropriate permissions on the remote server to access the SLA on the remote element.