SLA

To speed up SLA reports in Longitude 6.2.1, the data for the report is first summarized and written to a summary table - reports are run from this summary table.

If you try to run a report that does not use the same time selections written to the summary table, the report will display an error message that data is missing. Reports without a time selection (running from 00:00 --> 23:59) will display without this error.

To display SLA reports for specific time periods, define the SLA collection times to only be during the times of interest.

Longitude 6.2 provides two default SLAs for all Longitude versions: Unix CPU SLA and Windows CPU SLA. These SLAs track the CPU performance on the first 5 Unix/Linux computers monitored, and the first 5 Windows computers monitored, respectively, and will display "degraded" if a tracked computer has CPU > 80% or "unacceptable" for CPU > 90%.

There can be a problem viewing the detail page for a down SLA in IE - when you try to get the details, the status bar will display "Downloading data http://0.0.0.0/...", and then the display an incorrect detail report.

The work around for the "Downloading data http://0.0.0.0/..." message in IE for SLA details is:

1) Hit Ctrl-F5 - you should see "Done" in the status bar
2) Click the "Back" button in the browser
3) Now you should either see the correct page, or a "Webpage has expired" page
4) If you see "Webpage has expired": click "Back" button on the browser, and re-run the report.

There is currently no way to define an SLA maintenance schedule with a time range that spans 2 days (e.g. 11 PM - 1 AM). This will be addressed in a future release.

In the meantime, you can use a combination of a maintenance schedule and an SLA suspension to span 2 days. For example, set up a maintenance schedule from 23:00 to 23:59 and then use the Suspend SLA function to suspend the SLA between 00:00 and 01:00.

After an upgrade to Longitude 5.1, SLA reports do not contain detail data. The SLA dashboard works correctly, but the reports are missing data.

Please contact Heroix Support for the fix (reference case 3114), or upgrade to the latest Longitude release.