SLA

If you try to create a SLA and add a computer for a Transaction other than Ping it does not give you the list of computers to select:

Please follow the steps below, this will then give you the option to select the appropiate computers and instances.

1. Download the index-all.js file
2. Go to Longitude\tomcat\webapps\webui\web2.0\javascripts and rename the existing file to index-all.js to index-all.orig and save the new file to this location
   

If you try to view a SLA in the 2.0 UI and you get the error listed below:

Request URI:/web2.0/runSlaDashboardDetail.do
Jsp URI:/jsp/common/exception/generalException.jsp

java.lang.NullPointerException

but you are still able to view the SLA in the Advanced UI:

Please follow the steps below and the SLA should display correctly.

1. Download the index-all.js file

IT cannot simply be viewed as a cost center; rather it needs to show value and its contribution to the bottom line. This is quite the challenge because when it is all said and done IT’s control over its own destiny is limited as its primary task is to recommend, deliver and maintain the appropriate technology and IT infrastructure so their organization can function properly and maintain a competitive edge.

So how does one quantify and show IT’s value to “management”? There are actually a few options:

Some of the VMware statistics have to be collected on specific schedules so the data is collected correctly.

Here is the list of statistics and the schedule they can run on.

VMware Cluster Memory: 15 minutes, 30 minutes, or 1 hour
VMware Datastore: 30 minutes or 1 hour

All other statistics can be collected on any other schedule but it is recommended not to run on the 5 min schedule.

If you have a SLA configured to only collect during a certain period of the day, the detail report may have inaccurate data in the time line data.

Please follow the steps below, to correct the SLA detail reports

1. Download the firenze-webui.jar file
2. Stop the Heroix Longitude WebUI service
3. Go to \Longitude\tomcat\webapps\webui\WEB-INF\lib and save the new file to this location, please let it overwrite the existing file

I am interested in running a sla report on a regular basis which is then published to the web so that any interested parties can view the report.

Ideally I would like to be able to publish this report to our own website, but if that is not achievable publishing the reports to the Heroix website would be fine. I can not find any tutorial videos on this subject nor any help in the user guide.

I would really appreciate a little direction in how I might accomplish this task.

Thank you in advance for the help.

--Mitch

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.