An SLA (or service level agreement) is a contract between providers of a service and its users, outlining the minimum level of acceptable service delivered. For example, if you wanted to host a website with a web hosting provider, oftentimes the web hosting company will tell you that they guarantee a certain percentage of uptime as part of their SLA. With Uptrends, you can monitor your SLA with a website, server, or web application provider or monitor an SLA you provide to your customers.
By creating an SLA definition, you can configure the same minimal requirements set by your provider and monitor them using the SLA overview dashboard that you find in the menu at Working with SLA data and reports.. If the site or service fails to meet the minimum requirements, it appears red in the SLA overview. For more information on the SLA overview dashboard see the article
The following elements are referred to as the SLA thresholds. Your SLA definition may include only uptime or any of the other SLA thresholds.
- Error uptime percentage – SLA uptime results lower than this threshold do not satisfy the SLA target: they will cause a red error in the SLA reports. Values higher than this threshold (but lower than the desired uptime percentage) will cause warnings in the SLA reporting.
- Desired uptime percentage – SLA uptime results with this value (or higher) are good; they satisfy the SLA target. Values between this threshold and the error uptime percentage will cause a yellow warning in the SLA reports.
- Page load time – The maximum page load time as agreed upon in the SLA.
- Operator response time – The amount of time between an Uptrends alert and the time that an operator logs into Uptrends and confirms the alert to indicate they are working on the situation. The Current alert status dashboard ( ) has the functionality for confirming an alert.
If you want to know more about how the uptime percentage is calculated, please read the knowledge base article Calculation of uptime and downtime.
In case your SLA isn’t active 24/7, for example if it only covers regular office hours, or if you have upcoming scheduled maintenance, you can add an SLA schedule. SLA schedules allow you to specify the times your SLA is active. Any downtime, increased load times, or errors outside of these times will not be taken account in the SLA reporting. You configure your SLA schedule on the Schedule tab, where you find the time schedule and the option to exclude days for planned maintenance.
Time schedule – For each hour of every day of the week, you can specify whether this SLA should be active or not.
Exclusion days – If you have non-routine planned downtime, you can exclude time based on specific calendar days and times.
Setting up an SLA definition
To define an SLA:
Click thebutton at the top right.
Give your definition a descriptive name.
Set the error uptime percentage in the yellow outlined box in the Uptime field. Uptime results below this value will be marked red on the SLA overview reports.
Set the green outlined box to the percentage where the uptime becomes a point of concern for meeting SLA compliance in the Uptime field. Uptime results between this and the error uptime percentage will be marked yellow on the SLA overview reports.
(Optional) If required by your SLA, adjust the Page load time and/or Operator response time.
(Optional) If your SLA isn’t always active, set up a schedule. In the timetable on the Schedule tab the blue squares indicate that the SLA is active at that time while white squares indicate an inactive timeslot. Click on a square to switch between active and inactive. If you want to disable entire days or the same hour of each day, click on the column or row headers instead of individual squares.
(Optional) For planned downtime (beyond the time schedule), add exclusion days on the Schedule tab:
- Click the button.
- Give the exclusion period a descriptive name.
- Select the start and end dates and times in the From and Until fields.
- Click .
Click thebutton at the bottom left.