{"id":4278,"date":"2013-11-07T17:00:56","date_gmt":"2013-11-07T23:00:56","guid":{"rendered":"https:\/\/dcmblogmulti.wpengine.com\/?p=4278"},"modified":"2026-05-14T11:32:27","modified_gmt":"2026-05-14T11:32:27","slug":"sla-management-101","status":"publish","type":"post","link":"https:\/\/www.dotcom-monitor.com\/blog\/sla-management-101\/","title":{"rendered":"SLA Management 101: How to Create a Meaningful Web Performance SLA"},"content":{"rendered":"
In the past five years the number of externally hosted elements on the webpages of the top 1,000 websites has more than doubled, according to a report by WebsiteOptimization.\u00a0Moreover, as the\u00a0 number of third-party hosts associated with websites continues to increase, Service Level Agreements (SLA) attached to those third-party hosted elements have also increased in importance. Determining the performance of third-party hosted applications and webpage elements can be a challenge. The reason is those third-party hosted elements are impacted by network conditions, page conditions and server issues. In order to provide effective SLA\u00a0 management information, a performance monitoring solution needs to take all of these factors \u2013\u00a0the network, webpage, and server \u2013\u00a0into account. As SLA management directly impacts the revenues and business relations between two companies, the quality of the monitoring tool must be high.<\/p>\n <\/p>\n Below are two distinctions of “high-quality monitoring” to to look for when employing monitoring as part of SLA management strategy:<\/p>\n Once you understand what quality monitoring looks like technically, the next step is mapping those checks to contractual commitments \u2014 our guide to SLA compliance for SaaS businesses<\/a> covers which components to monitor and how to structure reports for audits.<\/p>\n When used for SLA management, performance monitoring has both reactive and proactive goals. Here are three examples of it’s use:<\/p>\n For a detailed walkthrough of how Dotcom-Monitor specifically implements these reactive and proactive functions, see our article on using Dotcom-Monitor for SLA compliance<\/a> \u2014 including a real-world case study.<\/p>\n For the customers of service providers who are relying on SLAs, the purpose of monitoring focuses on validating deliverables<\/strong>. In other words, customers need to make sure a service provider is meeting the SLA expectations outlined. Other critical elements delivered by SLA monitoring include error forensics capabilities, which can be used to determine if and when SLA have failed to meet expectations. A monitoring service should also deliver detailed reports on usage and availability that can be used to determine return on investment (ROI) and total cost of ownership (TCO) when it comes to using these third-party services. For further samples, see the Dotcom-Monitor Wiki article on SLA reports<\/a>.<\/p>\n Find more on Dotcom-Monitor SLA Management<\/strong> here.<\/p>\n For a comprehensive set of 11 tactics that support both goals, our guide to web application monitoring best practices<\/a> covers everything from setting SLOs to auditing third-party tag impact.<\/p>\n
<\/a><\/p>\nWhat do we mean by high quality monitoring?<\/h2>\n
\n
Using Web Monitoring Tools for SLA Management<\/h2>\n
\n
