{"_id":"5b9074f65bc30b00039afa16","project":"5633ebff7e9e880d00af1a53","version":{"_id":"5a8fae0268264c001f20cc00","project":"5633ebff7e9e880d00af1a53","__v":4,"createdAt":"2018-02-23T06:00:34.961Z","releaseDate":"2018-02-23T06:00:34.961Z","categories":["5a8fae0268264c001f20cc01","5a8fae0268264c001f20cc02","5a8fae0368264c001f20cc03","5a8fae0368264c001f20cc04","5a8fae0368264c001f20cc05","5a8fae0368264c001f20cc06","5a8fae0368264c001f20cc07","5a8fae0368264c001f20cc08","5a8fae0368264c001f20cc09","5abaa7eb72d6dc0028a07bf3","5b8ee7842790f8000333f9ba","5b8ee8f244a21a00034b5cd9"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"2.0.0","version":"2.0"},"category":{"_id":"5a8fae0368264c001f20cc04","version":"5a8fae0268264c001f20cc00","project":"5633ebff7e9e880d00af1a53","__v":0,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-05-31T04:26:39.925Z","from_sync":false,"order":5,"slug":"versions","title":"Bonsai.io Platform"},"user":"5ab13dd42459e0004e761001","__v":0,"parentDoc":null,"updates":[],"next":{"pages":[],"description":""},"createdAt":"2018-09-06T00:29:42.316Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":11,"body":"Bonsai's support policy categorizes incident severity into three tiers. You can use these severity levels to help communicate the level of support needed.\n[block:callout]\n{\n  \"type\": \"info\",\n  \"title\": \"24/7 Operational Coverage is Provided for All Clusters\",\n  \"body\": \"Bonsai monitors its infrastructure 24 hours a day, 365 days a year. The Operations Team is automatically alerted to any problems in real time. One or more engineers will then respond to the event. These types of events include, but are not limited to:\\n\\n- Red Indexes\\n- Failed EC2 Instances\\n- Stuck GC\\n- Failed backups\\n- Network partitions / Split brain\\n\\nThis operational coverage is provided to all clusters, regardless of plan.\"\n}\n[/block]\nThe severity classifications are defined as:\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Severity Level\",\n    \"0-0\": \"**Severity 1**\",\n    \"0-1\": \"An incident of downtime or service degradation is causing severe impact to customer production availability. Active risk of data loss, traffic completely or mostly failing.\",\n    \"1-0\": \"**Severity 2**\",\n    \"1-1\": \"Moderate to severe service interruption that can be temporarily worked around. May cause a moderate to major degradation in user experience.\",\n    \"2-0\": \"**Severity 3**\",\n    \"2-1\": \"Low rate of minor service errors or intermittent degradations. Minor regressions to response times. Should be investigated and repaired but is not visibly harming customer’s production systems.\"\n  },\n  \"cols\": 2,\n  \"rows\": 3\n}\n[/block]\n\n[block:api-header]\n{\n  \"title\": \"Coverage Hours\"\n}\n[/block]\nIncidents not related to a problem Bonsai's infrastructure are treated as support issues. Coverage for these events is the same as our support hours:\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Severity Level\",\n    \"h-1\": \"Standard\",\n    \"h-2\": \"Business\",\n    \"h-3\": \"Enterprise\",\n    \"0-0\": \"**Severity 1**\",\n    \"1-0\": \"**Severity 2**\",\n    \"2-0\": \"**Severity 3**\",\n    \"0-3\": \"24/7\",\n    \"1-3\": \"Business hours\",\n    \"2-3\": \"Business hours\",\n    \"0-1\": \"Business hours\",\n    \"1-1\": \"Business hours\",\n    \"2-1\": \"Business hours\",\n    \"0-2\": \"Business hours\",\n    \"1-2\": \"Business hours\",\n    \"2-2\": \"Business hours\"\n  },\n  \"cols\": 4,\n  \"rows\": 3\n}\n[/block]\n\n[block:api-header]\n{\n  \"title\": \"Response Time\"\n}\n[/block]\nWe will respond to inquiries about active incidents within these time windows.\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Severity Level\",\n    \"h-1\": \"Standard\",\n    \"h-2\": \"Business\",\n    \"h-3\": \"Enterprise\",\n    \"0-0\": \"**Severity 1**\",\n    \"1-0\": \"**Severity 2**\",\n    \"2-0\": \"**Severity 3**\",\n    \"0-1\": \"8 hrs\",\n    \"0-2\": \"1 hr\",\n    \"0-3\": \"1 hr\",\n    \"1-1\": \"24 hrs\",\n    \"1-2\": \"4 hrs\",\n    \"1-3\": \"4 hrs\",\n    \"2-1\": \"48 hrs\",\n    \"2-2\": \"8 hrs\",\n    \"2-3\": \"8 hrs\"\n  },\n  \"cols\": 4,\n  \"rows\": 3\n}\n[/block]","excerpt":"","slug":"incident-response-times","type":"basic","title":"Incident Response Times"}

Incident Response Times


Bonsai's support policy categorizes incident severity into three tiers. You can use these severity levels to help communicate the level of support needed. [block:callout] { "type": "info", "title": "24/7 Operational Coverage is Provided for All Clusters", "body": "Bonsai monitors its infrastructure 24 hours a day, 365 days a year. The Operations Team is automatically alerted to any problems in real time. One or more engineers will then respond to the event. These types of events include, but are not limited to:\n\n- Red Indexes\n- Failed EC2 Instances\n- Stuck GC\n- Failed backups\n- Network partitions / Split brain\n\nThis operational coverage is provided to all clusters, regardless of plan." } [/block] The severity classifications are defined as: [block:parameters] { "data": { "h-0": "Severity Level", "0-0": "**Severity 1**", "0-1": "An incident of downtime or service degradation is causing severe impact to customer production availability. Active risk of data loss, traffic completely or mostly failing.", "1-0": "**Severity 2**", "1-1": "Moderate to severe service interruption that can be temporarily worked around. May cause a moderate to major degradation in user experience.", "2-0": "**Severity 3**", "2-1": "Low rate of minor service errors or intermittent degradations. Minor regressions to response times. Should be investigated and repaired but is not visibly harming customer’s production systems." }, "cols": 2, "rows": 3 } [/block] [block:api-header] { "title": "Coverage Hours" } [/block] Incidents not related to a problem Bonsai's infrastructure are treated as support issues. Coverage for these events is the same as our support hours: [block:parameters] { "data": { "h-0": "Severity Level", "h-1": "Standard", "h-2": "Business", "h-3": "Enterprise", "0-0": "**Severity 1**", "1-0": "**Severity 2**", "2-0": "**Severity 3**", "0-3": "24/7", "1-3": "Business hours", "2-3": "Business hours", "0-1": "Business hours", "1-1": "Business hours", "2-1": "Business hours", "0-2": "Business hours", "1-2": "Business hours", "2-2": "Business hours" }, "cols": 4, "rows": 3 } [/block] [block:api-header] { "title": "Response Time" } [/block] We will respond to inquiries about active incidents within these time windows. [block:parameters] { "data": { "h-0": "Severity Level", "h-1": "Standard", "h-2": "Business", "h-3": "Enterprise", "0-0": "**Severity 1**", "1-0": "**Severity 2**", "2-0": "**Severity 3**", "0-1": "8 hrs", "0-2": "1 hr", "0-3": "1 hr", "1-1": "24 hrs", "1-2": "4 hrs", "1-3": "4 hrs", "2-1": "48 hrs", "2-2": "8 hrs", "2-3": "8 hrs" }, "cols": 4, "rows": 3 } [/block]