{"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-11-12T21:58:16","modified_gmt":"2026-11-12T21:58:16","slug":"sla-management-101","status":"publish","type":"post","link":"https:\/\/www.dotcom-monitor.com\/blog\/sla-management-101\/","title":{"rendered":"SLA Monitoring: How to Track Service Levels and Prevent Breaches"},"content":{"rendered":"<p><img fetchpriority=\"high\" decoding=\"async\" class=\"alignright wp-image-34912\" src=\"https:\/\/www.dotcom-monitor.com\/blog\/wp-content\/uploads\/sites\/3\/2013\/11\/sla-monitoring-hero.webp\" alt=\"Operations engineer reviewing an SLA monitoring dashboard with monthly uptime, response time and remaining error budget\" width=\"380\" height=\"214\" srcset=\"https:\/\/www.dotcom-monitor.com\/blog\/wp-content\/uploads\/sites\/3\/2013\/11\/sla-monitoring-hero.webp 1200w, https:\/\/www.dotcom-monitor.com\/blog\/wp-content\/uploads\/sites\/3\/2013\/11\/sla-monitoring-hero-300x169.webp 300w, https:\/\/www.dotcom-monitor.com\/blog\/wp-content\/uploads\/sites\/3\/2013\/11\/sla-monitoring-hero-1024x576.webp 1024w, https:\/\/www.dotcom-monitor.com\/blog\/wp-content\/uploads\/sites\/3\/2013\/11\/sla-monitoring-hero-768x432.webp 768w\" sizes=\"(max-width: 380px) 100vw, 380px\" \/>SLA monitoring is the continuous measurement of a service&#8217;s availability, response time and error rate against the targets written into a service level agreement (SLA), using automated checks that run around the clock and alerts that fire while there is still time to fix a problem before it becomes a breach.<\/p>\n<p>A missed target costs more than the service credit in the contract. Customers who claim credits often reopen renewal terms, and the account team needs numbers it can defend. The <a href=\"https:\/\/www.dotcom-monitor.com\/blog\/what-is-the-cost-of-downtime\/\">cost of downtime<\/a> adds lost sales and support hours on top.<\/p>\n<p>This guide covers the metrics worth tracking, a six-step compliance process, monthly reporting and the mistakes that make SLA numbers wrong.<\/p>\n<div>\n<p><strong>Key Takeaways<\/strong><\/p>\n<ul>\n<li>An SLA is the contract, an SLO is the tighter internal target (for example 99.95% against a 99.9% SLA) and an SLI is the measured value.<\/li>\n<li>A 99.9% uptime SLA allows 43.2 minutes of downtime a month, and 99.99% allows 4.3 minutes.<\/li>\n<li>Measure from outside your network, with at least two locations in every region the SLA covers and one-minute checks for 99.9% or stricter.<\/li>\n<li>Alert on the error budget (warn at 50% used, page at 75%) instead of waiting for the breach.<\/li>\n<li>Report uptime against target, every incident with timestamps and excluded maintenance separately.<\/li>\n<\/ul>\n<h2 id='what-is-sla-monitoring'  id=\"boomdevs_1\" id=\"what-is-sla-monitoring\">What Is SLA Monitoring?<\/h2>\n<p>SLA monitoring tracks the service levels a provider has promised in writing and compares measured results with those promises. For a website, application or API, that means checking availability, response time and error rate on a fixed schedule, recording every failure with timestamps and reporting the results for each SLA period.<\/p>\n<p>SLA stands for service level agreement. It&#8217;s the contract, or the section of a contract, that defines the service a customer can expect, how it will be measured and what the provider owes when it falls short. The remedy is usually a service credit.<\/p>\n<p>Three groups rely on SLA monitoring. SaaS and hosting providers use it to prove they kept their commitments. IT teams use it to hold their own vendors (cloud hosts, CDNs, payment gateways) to theirs. And internal IT departments use it to report against the service levels they agreed with business units.<\/p>\n<p>Help desk SLAs, such as a first response to a ticket within one hour, live in ITSM software. This guide covers SLAs for websites, applications and APIs, where the numbers come from checks against the running service.<\/p>\n<h2 id='sla-vs-slo-vs-sli-and-kpis'  id=\"boomdevs_2\" id=\"sla-vs-slo-vs-sli-and-kpis\">SLA vs SLO vs SLI (and KPIs)<\/h2>\n<p>An SLA is the promise, an SLO is the internal target and an SLI is the measurement.<\/p>\n<div class=\"table-wrap\">\n<table>\n<thead>\n<tr>\n<th>Term<\/th>\n<th>What it is<\/th>\n<th>Example<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>SLA (service level agreement)<\/td>\n<td>The external commitment, with consequences when it&#8217;s missed<\/td>\n<td>99.9% monthly uptime, with a 10% service credit below that<\/td>\n<\/tr>\n<tr>\n<td>SLO (service level objective)<\/td>\n<td>The internal target, set tighter than the SLA to leave a buffer<\/td>\n<td>99.95% monthly availability<\/td>\n<\/tr>\n<tr>\n<td>SLI (service level indicator)<\/td>\n<td>The measured value you compare with the SLO<\/td>\n<td>Measured availability this month: 99.97% of checks succeeded<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p>The SLO sits above the SLA on purpose. Engineering gets an early warning at 99.95%, and the customer-facing promise of 99.9% stays intact. The room between 100% and the SLO is your error budget, 0.05% of a 30-day month or about 21.6 minutes.<\/p>\n<p><img decoding=\"async\" class=\"alignnone size-full wp-image-34913\" src=\"https:\/\/www.dotcom-monitor.com\/blog\/wp-content\/uploads\/sites\/3\/2013\/11\/sla-slo-sli.webp\" alt=\"Diagram comparing an SLA of 99.9 percent, an SLO of 99.95 percent and a measured SLI of 99.97 percent, with the error budget between them\" width=\"1200\" height=\"675\" srcset=\"https:\/\/www.dotcom-monitor.com\/blog\/wp-content\/uploads\/sites\/3\/2013\/11\/sla-slo-sli.webp 1200w, https:\/\/www.dotcom-monitor.com\/blog\/wp-content\/uploads\/sites\/3\/2013\/11\/sla-slo-sli-300x169.webp 300w, https:\/\/www.dotcom-monitor.com\/blog\/wp-content\/uploads\/sites\/3\/2013\/11\/sla-slo-sli-1024x576.webp 1024w, https:\/\/www.dotcom-monitor.com\/blog\/wp-content\/uploads\/sites\/3\/2013\/11\/sla-slo-sli-768x432.webp 768w\" sizes=\"(max-width: 1200px) 100vw, 1200px\" \/><\/p>\n<p><strong>SLA vs KPI.<\/strong> A KPI (key performance indicator) is any metric a team tracks, with no outside promise. Median page load time can be a KPI the web team watches. It becomes an SLA metric only when it&#8217;s written into an agreement with a remedy attached.<\/p>\n<h2 id='what-are-the-three-types-of-slas'  id=\"boomdevs_3\" id=\"what-are-the-three-types-of-slas\">What Are the Three Types of SLAs?<\/h2>\n<p>The three types of SLA are customer-based, service-based and multi-level. ITIL defines them this way:<\/p>\n<ul>\n<li><strong>Customer-based SLA.<\/strong> One agreement covers every service a single customer uses. Example: a managed service provider&#8217;s single contract with a hospital for its patient portal hosting, email and help desk.<\/li>\n<li><strong>Service-based SLA.<\/strong> One agreement per service, with the same terms for every customer. Example: a SaaS company&#8217;s public 99.9% uptime commitment that applies to all subscribers.<\/li>\n<li><strong>Multi-level SLA.<\/strong> Terms come in layers, with a corporate level that applies to everyone, a customer level and a service level. Example: a cloud provider&#8217;s company-wide uptime commitment, plus extra terms for one enterprise customer and a target for its API gateway.<\/li>\n<\/ul>\n<h2 id='key-sla-metrics-to-monitor'  id=\"boomdevs_4\" id=\"key-sla-metrics-to-monitor\">Key SLA Metrics to Monitor<\/h2>\n<p>Availability gets most of the attention, but a service can be up and still miss its SLA on speed or errors. These SLA metrics cover the common commitments for websites, applications and APIs. The targets below are examples, not benchmarks. Set yours from your own baseline and contract.<\/p>\n<div class=\"table-wrap\">\n<table>\n<thead>\n<tr>\n<th>Metric<\/th>\n<th>What it measures<\/th>\n<th>Example target<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Availability (uptime %)<\/td>\n<td>Share of checks or minutes in the period where the service responded correctly<\/td>\n<td>99.9% to 99.99% per month<\/td>\n<\/tr>\n<tr>\n<td>Response time (p95)<\/td>\n<td>The 95th percentile, or the time within which 95% of requests complete. Outliers distort it less than an average<\/td>\n<td>Under 1 second for an API call, under 3 seconds for a full page<\/td>\n<\/tr>\n<tr>\n<td>Error rate<\/td>\n<td>Share of requests that return 5xx errors, time out or fail a content check<\/td>\n<td>Under 0.1% to 1%<\/td>\n<\/tr>\n<tr>\n<td>Transaction success rate<\/td>\n<td>Share of multi-step journeys (login, search, checkout) that complete end to end<\/td>\n<td>99% or higher<\/td>\n<\/tr>\n<tr>\n<td>MTTD (mean time to detect)<\/td>\n<td>Time from the start of a failure to the first alert<\/td>\n<td>Under 5 minutes<\/td>\n<\/tr>\n<tr>\n<td>MTTR (mean time to resolve)<\/td>\n<td>Time from the first alert to restored service (define the start point in your reporting policy)<\/td>\n<td>Set by severity, often 1 to 4 hours for the most severe incidents<\/td>\n<\/tr>\n<tr>\n<td>Third-party and API availability<\/td>\n<td>Uptime of dependencies you don&#8217;t run, such as payment, identity, DNS and CDN providers<\/td>\n<td>At least the vendor&#8217;s own SLA<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p>MTTD and MTTR rarely appear in contracts, but they decide whether you hit the availability number. Every minute before the alert is downtime nobody is working on.<\/p>\n<p>An uptime percentage sounds generous until you convert it to minutes. Here is the allowed downtime for common uptime SLA targets, based on a 30-day month and a 365-day year:<\/p>\n<div class=\"table-wrap\">\n<table>\n<thead>\n<tr>\n<th>Uptime SLA<\/th>\n<th>Allowed downtime per month<\/th>\n<th>Allowed downtime per year<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>99%<\/td>\n<td>7 hours 12 minutes<\/td>\n<td>3 days 15.6 hours<\/td>\n<\/tr>\n<tr>\n<td>99.5%<\/td>\n<td>3 hours 36 minutes<\/td>\n<td>43.8 hours<\/td>\n<\/tr>\n<tr>\n<td>99.9%<\/td>\n<td>43.2 minutes<\/td>\n<td>8.76 hours<\/td>\n<\/tr>\n<tr>\n<td>99.95%<\/td>\n<td>21.6 minutes<\/td>\n<td>4.38 hours<\/td>\n<\/tr>\n<tr>\n<td>99.99%<\/td>\n<td>4.3 minutes<\/td>\n<td>52.6 minutes<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p>For other targets or periods, use the <a href=\"https:\/\/www.dotcom-monitor.com\/downtime-to-uptime-calculator\/\">downtime to uptime calculator<\/a>.<\/p>\n<h2 id='how-to-monitor-sla-compliance-step-by-step'  id=\"boomdevs_5\" id=\"how-to-monitor-sla-compliance-step-by-step\">How to Monitor SLA Compliance, Step by Step<\/h2>\n<p>SLA compliance monitoring comes down to six steps that turn a contract clause into numbers you can track daily and report monthly.<\/p>\n<h3 id='step-1-turn-the-sla-into-measurable-slis'  id=\"boomdevs_6\" id=\"step-1-turn-the-sla-into-measurable-slis\">Step 1: Turn the SLA Into Measurable SLIs<\/h3>\n<p>Read the contract and write each commitment as a measurement. Name what is checked, from where and how often, what counts as a failure and which period applies. For an API, &#8220;99.9% availability&#8221; might mean the share of one-minute checks against the orders endpoint that return HTTP 200 with valid JSON within 10 seconds, from three locations, per calendar month in UTC. If the contract doesn&#8217;t define &#8220;available,&#8221; agree on a definition with the customer before the first report.<\/p>\n<h3 id='step-2-monitor-externally-from-several-locations'  id=\"boomdevs_7\" id=\"step-2-monitor-externally-from-several-locations\">Step 2: Monitor Externally From Several Locations<\/h3>\n<p>Customers reach your service through DNS, CDNs, ISPs and certificates that internal checks never touch. High-quality monitoring for SLAs accounts for the network, the page and the server, because every customer request depends on all three. External synthetic checks run the same requests customers make, from outside your network, and produce evidence neither party controls.<\/p>\n<p>Agree on the location rule before reporting starts. Some SLAs count a failed minute only when more than one location fails, while others count a regional failure if customers in that region couldn&#8217;t use the service. Either way, report each region separately. In a typical case, the load balancer health check stays green while users in one region time out at a CDN edge, and only checks from that region record the failure. Run at least two locations in every region the SLA covers so a regional outage can still be confirmed.<\/p>\n<h3 id='step-3-match-check-frequency-to-the-sla-window'  id=\"boomdevs_8\" id=\"step-3-match-check-frequency-to-the-sla-window\">Step 3: Match Check Frequency to the SLA Window<\/h3>\n<p>Each check is a sample. With five-minute checks, a three-minute outage can disappear between checks, and two tools reading the same raw results can report different durations because they round to different intervals. A 99.99% monthly SLA allows 4.3 minutes of downtime, so five-minute checks can&#8217;t measure that budget accurately. Run one-minute checks for anything at 99.9% or stricter.<\/p>\n<h3 id='step-4-alert-before-a-breach-using-the-error-budget'  id=\"boomdevs_9\" id=\"step-4-alert-before-a-breach-using-the-error-budget\">Step 4: Alert Before a Breach Using the Error Budget<\/h3>\n<p>An alert at the moment of breach is too late to help. Alert on the error budget instead. With a 99.95% SLO, the monthly budget is 21.6 minutes. Warn the team at 50% used (about 11 minutes), page the on-call engineer at 75% and escalate when the SLO is gone, which still leaves about 22 minutes (43.2 minus 21.6) before the 99.9% SLA is breached. Fast burns need their own rule. If a tenth of the month&#8217;s budget disappears within an hour, page right away instead of waiting for the 75% line. The <a href=\"https:\/\/www.dotcom-monitor.com\/sla-breach-calculator\/\">SLA breach calculator<\/a> shows how much downtime a target leaves.<\/p>\n<h3 id='step-5-handle-maintenance-windows-and-agreed-exclusions'  id=\"boomdevs_10\" id=\"step-5-handle-maintenance-windows-and-agreed-exclusions\">Step 5: Handle Maintenance Windows and Agreed Exclusions<\/h3>\n<p>Most SLAs exclude announced maintenance, outages the customer caused and events outside the provider&#8217;s control. Schedule maintenance windows in your monitoring tool so that time is labeled as excluded rather than deleted, and keep the raw results. Don&#8217;t stretch a maintenance window after an incident to cover it unless the contract and the customer notice allow it. Unannounced &#8220;emergency maintenance&#8221; usually counts as downtime.<\/p>\n<h3 id='step-6-report-and-review-monthly'  id=\"boomdevs_11\" id=\"step-6-report-and-review-monthly\">Step 6: Report and Review Monthly<\/h3>\n<p>Generate the report when the SLA period closes and review it with the service owners. Web monitoring tools for SLA management flag errors as they happen, document whether the SLA was met and help show where an outage started (your service or a third party) when credits or charge-backs are disputed. Adjust SLOs and alert thresholds for the next period. For contract and audit details specific to SaaS, see <a href=\"https:\/\/www.dotcom-monitor.com\/blog\/sla-compliance-for-saas-businesses\/\">SLA compliance for SaaS businesses<\/a>.<\/p>\n<p><img decoding=\"async\" class=\"alignnone size-full wp-image-34914\" src=\"https:\/\/www.dotcom-monitor.com\/blog\/wp-content\/uploads\/sites\/3\/2013\/11\/error-budget-burn.webp\" alt=\"Chart of a monthly error budget burning down, with a warning at 50 percent used, a page at 75 percent and the SLA breach point marked\" width=\"1200\" height=\"675\" srcset=\"https:\/\/www.dotcom-monitor.com\/blog\/wp-content\/uploads\/sites\/3\/2013\/11\/error-budget-burn.webp 1200w, https:\/\/www.dotcom-monitor.com\/blog\/wp-content\/uploads\/sites\/3\/2013\/11\/error-budget-burn-300x169.webp 300w, https:\/\/www.dotcom-monitor.com\/blog\/wp-content\/uploads\/sites\/3\/2013\/11\/error-budget-burn-1024x576.webp 1024w, https:\/\/www.dotcom-monitor.com\/blog\/wp-content\/uploads\/sites\/3\/2013\/11\/error-budget-burn-768x432.webp 768w\" sizes=\"(max-width: 1200px) 100vw, 1200px\" \/><\/p>\n<h2 id='what-should-sla-reporting-include'  id=\"boomdevs_12\" id=\"what-should-sla-reporting-include\">What Should SLA Reporting Include?<\/h2>\n<p>An SLA report serves the customer, who wants to know if the promise was kept, and the engineers, who need to know what to fix. Include:<\/p>\n<ul>\n<li><strong>Uptime percentage against the target<\/strong> for the period, with a clear met or missed status.<\/li>\n<li><strong>An incident list<\/strong> with start time, end time, duration, affected service and cause. A typical entry reads &#8220;March 14, 02:10 to 02:31 UTC, 21 minutes, checkout API, database failover, counted against the SLA.&#8221;<\/li>\n<li><strong>Excluded time<\/strong> listed separately, with the maintenance notice or contract clause that justifies each exclusion.<\/li>\n<li><strong>Results for each location and each service<\/strong>, so a regional or single-service problem is visible.<\/li>\n<li><strong>A trend against the previous period<\/strong> for uptime and p95 response time.<\/li>\n<\/ul>\n<p>Send it on a fixed schedule, usually as PDF, with CSV for anyone who wants to analyze the data. Sample <a href=\"https:\/\/www.dotcom-monitor.com\/features\/uptime-and-sla-reports\/\">SLA reports<\/a> follow this layout, and this walkthrough shows how to <a href=\"https:\/\/www.dotcom-monitor.com\/wiki\/knowledge-base\/sla-report\/\">create an SLA report<\/a> with targets, schedules and filters.<\/p>\n<h2 id='common-sla-monitoring-mistakes'  id=\"boomdevs_13\" id=\"common-sla-monitoring-mistakes\">Common SLA Monitoring Mistakes<\/h2>\n<p>The most common mistakes come from measuring in the wrong place, sampling too coarsely or alerting too late:<\/p>\n<ul>\n<li><strong>Measuring only from inside your network.<\/strong> Internal checks skip DNS, CDN and ISP problems that customers hit first.<\/li>\n<li><strong>Using a single location.<\/strong> One location can&#8217;t tell a regional outage from a global one, and a problem at that location looks like your downtime.<\/li>\n<li><strong>Letting averages hide spikes.<\/strong> A 400 ms monthly average can include an hour of 8-second responses. Report p95 or p99.<\/li>\n<li><strong>Getting maintenance exclusions wrong.<\/strong> Forget to exclude an announced window and you report downtime you don&#8217;t owe. Exclude unannounced work and the customer&#8217;s own logs won&#8217;t match yours.<\/li>\n<li><strong>Ignoring third-party dependencies.<\/strong> If checkout depends on a payment API, its outages are your downtime unless the contract says otherwise. Monitor it separately to show where the failure was.<\/li>\n<li><strong>No alert before the breach.<\/strong> Without error budget alerts, the first sign of trouble is the monthly report.<\/li>\n<\/ul>\n<h2 id='what-should-you-look-for-in-an-sla-monitoring-tool'  id=\"boomdevs_14\" id=\"what-should-you-look-for-in-an-sla-monitoring-tool\">What Should You Look for in an SLA Monitoring Tool?<\/h2>\n<p>A tool built for SLA work measures from outside your infrastructure, warns before a breach and produces reports customers accept. Look for:<\/p>\n<ul>\n<li>External synthetic checks that run outside your own infrastructure<\/li>\n<li>Monitoring locations in the regions where your customers are<\/li>\n<li>One-minute check intervals for strict SLAs<\/li>\n<li>Threshold and error budget alerts with escalation<\/li>\n<li>Maintenance windows that exclude time without deleting data<\/li>\n<li>Scheduled SLA reports in PDF and CSV<\/li>\n<li>API checks and multi-step transaction checks, not just page pings<\/li>\n<\/ul>\n<p>Three categories of tool show up in SLA work. Synthetic monitoring tools measure availability from outside, APM tools measure performance from inside the application code, and ITSM platforms track ticket SLAs. For website and API SLAs, the reported number usually comes from synthetic monitoring.<\/p>\n<p>Dotcom-Monitor is one example of a synthetic monitoring tool used for SLA tracking. It runs <a href=\"https:\/\/www.dotcom-monitor.com\/solutions\/uptime\/\">uptime monitoring<\/a> from 33 locations in 18 countries, checks as often as once a minute, and builds SLA reports with an uptime target, scheduled maintenance exclusions and filters that count an error only when several locations report it. Reports go out daily, weekly, monthly or quarterly as PDF or CSV. API checks and recorded browser transactions feed the same reports. For the provider side of these reports, see how <a href=\"https:\/\/www.dotcom-monitor.com\/blog\/dotcom-monitor-sla-compliance\/\">Dotcom-Monitor supports SLA compliance<\/a>.<\/p>\n<section class=\"final-cta\">\n<h2 id='how-do-you-start-tracking-slas-with-dotcom-monitor'  id=\"boomdevs_15\" id=\"how-do-you-start-tracking-slas-with-dotcom-monitor\">How Do You Start Tracking SLAs With Dotcom-Monitor?<\/h2>\n<p>Start with your strictest SLA. Define its SLIs, check it every minute from at least three locations and set a 50% error budget warning before the next period begins. <a href=\"https:\/\/userauth.dotcom-monitor.com\/Account\/FreeTrialSignUp?SolutionType=Monitoring\">Dotcom-Monitor&#8217;s free trial<\/a> includes <a href=\"https:\/\/www.dotcom-monitor.com\/features\/uptime-and-sla-reports\/\">SLA reports<\/a>, maintenance scheduling and alerting, with no credit card required, so your first monthly report can come from independent data.<\/p>\n<\/section>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>We explore the distinctions of &#8220;high-quality monitoring&#8221; and outline what to look for when employing monitoring as part of an SLA management strategy.<\/p>\n","protected":false},"author":21,"featured_media":34762,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-4278","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.dotcom-monitor.com\/blog\/wp-json\/wp\/v2\/posts\/4278","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dotcom-monitor.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dotcom-monitor.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dotcom-monitor.com\/blog\/wp-json\/wp\/v2\/users\/21"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dotcom-monitor.com\/blog\/wp-json\/wp\/v2\/comments?post=4278"}],"version-history":[{"count":0,"href":"https:\/\/www.dotcom-monitor.com\/blog\/wp-json\/wp\/v2\/posts\/4278\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dotcom-monitor.com\/blog\/wp-json\/wp\/v2\/media\/34762"}],"wp:attachment":[{"href":"https:\/\/www.dotcom-monitor.com\/blog\/wp-json\/wp\/v2\/media?parent=4278"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dotcom-monitor.com\/blog\/wp-json\/wp\/v2\/categories?post=4278"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dotcom-monitor.com\/blog\/wp-json\/wp\/v2\/tags?post=4278"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}