Deployed ac0e045 with MkDocs version: 0.16.1
This commit is contained in:
Marius Pana
parent
1e5053abd6
commit
8855265bdd
|
|
@ -72,7 +72,7 @@
|
|||
},
|
||||
{
|
||||
"location": "/oncall/alerting_principles/",
|
||||
"text": "We manage how we get alerted based on many factors such as the customers contractual SLA, the urgency of their request or incident, etc.. \nan alert or notification is something which requires a human to perform an action\n. Based on the severity of the issue (service request or incident) we prioritize accordingly in \nDoIT\n.\n\n\n\n\nMajor Priority Alerts\n\n\nAnything that wakes up a human in the middle of the night should be \nimmediately human actionable\n. If it is none of those things, then we need to adjust the alert to not page at those times.\n\n\n\n\n\n\n\n\n\n\nPriority\n\n\nAlerts\n\n\nResponse\n\n\n\n\n\n\n\n\n\n\nMajor\n\n\nMajor-Priority Spearhead Alert 24/7/365.\n\n\nRequires \nimmediate human action\n.\n\n\n\n\n\n\nNormal\n\n\nNormal-Priority Spearhead Alert during \nbusiness hours only\n.\n\n\nRequires human action that same working day.\n\n\n\n\n\n\nMinor\n\n\nMinor-Priority Spearhead Alert 24/7/365.\n\n\nRequires human action at some point.\n\n\n\n\n\n\n\n\nBoth IN and SR (incidents, service requests) share the same priorities. The actual response / resolution times vary and are based upon contractual agreements with the customer. These details (SLA) are available in DoIT on the organization page of the respective customer.\n\n\nIf you're setting up a new alert/notification, consider the chart above for how you want to alert people. Be mindful of not creating new high-priority alerts if they don't require an immediate response, for example.\n\n\n\n\nAlert Channels\n\n\nPresently we use email as the only notification method. This means keeping an eye on your email is essential!\nSMS and Push notifications are in the pipeline for DoIT. \n\n\n\n\nExamples\n#\n\n\n\"Production service is failing for 75% of requests, automation is unable to resolve.\"_\n#\n\n\nThis would be a \nMajor\n priority IN, requiring immediate human action to resolve.\n\n\n\n\n\"A customer sends an email stating that \"Production server disk space is filling, expected to be full in 48 hours. Log rotation is insufficient to resolve.\"\n#\n\n\nThis would be a \nNormal\n priority SR, requiring human action soon, but not immediately.\n\n\n\n\n\"An SSL certificate is due to expire in one week.\"\n#\n\n\nThis would be a \nMinor\n priority SR, requiring human action some time soon.",
|
||||
"text": "We manage how we get alerted based on many factors such as the customers contractual SLA, the urgency of their request or incident, etc.. \nan alert or notification is something which requires a human to perform an action\n. Based on the severity of the issue (service request or incident) we prioritize accordingly in \nDoIT\n.\n\n\n\n\nMajor Priority Alerts\n\n\nAnything that wakes up a human in the middle of the night should be \nimmediately human actionable\n. If it is none of those things, then we need to adjust the alert to not page at those times.\n\n\n\n\n\n\n\n\n\n\nPriority\n\n\nAlerts\n\n\nResponse\n\n\n\n\n\n\n\n\n\n\nMajor\n\n\nMajor-Priority Spearhead Alert 24/7/365.\n\n\nRequires \nimmediate human action\n.\n\n\n\n\n\n\nNormal\n\n\nNormal-Priority Spearhead Alert during \nbusiness hours only\n.\n\n\nRequires human action that same working day.\n\n\n\n\n\n\nMinor\n\n\nMinor-Priority Spearhead Alert 24/7/365.\n\n\nRequires human action at some point.\n\n\n\n\n\n\nNotification\n\n\nSuppressed Events. No response required.\n\n\nInformational only. We do not need these to clutter out ticketing or inboxes. If they are enabled they should be sent only to required/specific people, not groups.\n\n\n\n\n\n\n\n\nBoth IN and SR (incidents, service requests) share the same priorities. The actual response / resolution times vary and are based upon contractual agreements with the customer. These details (SLA) are available in DoIT on the organization page of the respective customer.\n\n\nIf you're setting up a new alert/notification, consider the chart above for how you want to alert people. Be mindful of not creating new high-priority alerts if they don't require an immediate response, for example.\n\n\n\n\nAlert Channels\n\n\nPresently we use email as the only notification method. This means keeping an eye on your email is essential!\nSMS and Push notifications are in the pipeline for DoIT. \n\n\n\n\nExamples\n#\n\n\n\"Production service is failing for 75% of requests, automation is unable to resolve.\"_\n#\n\n\nThis would be a \nMajor\n priority IN, requiring immediate human action to resolve.\n\n\n\n\n\"A customer sends an email stating that \"Production server disk space is filling, expected to be full in 48 hours. Log rotation is insufficient to resolve.\"\n#\n\n\nThis would be a \nNormal\n priority SR, requiring human action soon, but not immediately.\n\n\n\n\n\"An SSL certificate is due to expire in one week.\"\n#\n\n\nThis would be a \nMinor\n priority SR, requiring human action some time soon.",
|
||||
"title": "Alerting Principles"
|
||||
},
|
||||
{
|
||||
|
|
|
|||
|
|
@ -471,6 +471,11 @@
|
|||
<td>Minor-Priority Spearhead Alert 24/7/365.</td>
|
||||
<td>Requires human action at some point.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Notification</td>
|
||||
<td>Suppressed Events. No response required.</td>
|
||||
<td>Informational only. We do not need these to clutter out ticketing or inboxes. If they are enabled they should be sent only to required/specific people, not groups.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<p>Both IN and SR (incidents, service requests) share the same priorities. The actual response / resolution times vary and are based upon contractual agreements with the customer. These details (SLA) are available in DoIT on the organization page of the respective customer.</p>
|
||||
|
|
|
|||
34
sitemap.xml
34
sitemap.xml
|
|
@ -4,7 +4,7 @@
|
|||
|
||||
<url>
|
||||
<loc>https://response.spearhead.systems/</loc>
|
||||
<lastmod>2017-01-11</lastmod>
|
||||
<lastmod>2017-01-12</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
|
||||
|
|
@ -13,13 +13,13 @@
|
|||
|
||||
<url>
|
||||
<loc>https://response.spearhead.systems/oncall/being_oncall/</loc>
|
||||
<lastmod>2017-01-11</lastmod>
|
||||
<lastmod>2017-01-12</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
|
||||
<url>
|
||||
<loc>https://response.spearhead.systems/oncall/alerting_principles/</loc>
|
||||
<lastmod>2017-01-11</lastmod>
|
||||
<lastmod>2017-01-12</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
|
||||
|
|
@ -29,19 +29,19 @@
|
|||
|
||||
<url>
|
||||
<loc>https://response.spearhead.systems/before/severity_levels/</loc>
|
||||
<lastmod>2017-01-11</lastmod>
|
||||
<lastmod>2017-01-12</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
|
||||
<url>
|
||||
<loc>https://response.spearhead.systems/before/different_roles/</loc>
|
||||
<lastmod>2017-01-11</lastmod>
|
||||
<lastmod>2017-01-12</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
|
||||
<url>
|
||||
<loc>https://response.spearhead.systems/before/call_etiquette/</loc>
|
||||
<lastmod>2017-01-11</lastmod>
|
||||
<lastmod>2017-01-12</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
|
||||
|
|
@ -51,13 +51,13 @@
|
|||
|
||||
<url>
|
||||
<loc>https://response.spearhead.systems/during/during_an_incident/</loc>
|
||||
<lastmod>2017-01-11</lastmod>
|
||||
<lastmod>2017-01-12</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
|
||||
<url>
|
||||
<loc>https://response.spearhead.systems/during/security_incident_response/</loc>
|
||||
<lastmod>2017-01-11</lastmod>
|
||||
<lastmod>2017-01-12</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
|
||||
|
|
@ -67,13 +67,13 @@
|
|||
|
||||
<url>
|
||||
<loc>https://response.spearhead.systems/after/post_mortem_process/</loc>
|
||||
<lastmod>2017-01-11</lastmod>
|
||||
<lastmod>2017-01-12</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
|
||||
<url>
|
||||
<loc>https://response.spearhead.systems/after/post_mortem_template/</loc>
|
||||
<lastmod>2017-01-11</lastmod>
|
||||
<lastmod>2017-01-12</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
|
||||
|
|
@ -83,37 +83,37 @@
|
|||
|
||||
<url>
|
||||
<loc>https://response.spearhead.systems/training/overview/</loc>
|
||||
<lastmod>2017-01-11</lastmod>
|
||||
<lastmod>2017-01-12</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
|
||||
<url>
|
||||
<loc>https://response.spearhead.systems/training/incident_commander/</loc>
|
||||
<lastmod>2017-01-11</lastmod>
|
||||
<lastmod>2017-01-12</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
|
||||
<url>
|
||||
<loc>https://response.spearhead.systems/training/deputy/</loc>
|
||||
<lastmod>2017-01-11</lastmod>
|
||||
<lastmod>2017-01-12</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
|
||||
<url>
|
||||
<loc>https://response.spearhead.systems/training/scribe/</loc>
|
||||
<lastmod>2017-01-11</lastmod>
|
||||
<lastmod>2017-01-12</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
|
||||
<url>
|
||||
<loc>https://response.spearhead.systems/training/subject_matter_expert/</loc>
|
||||
<lastmod>2017-01-11</lastmod>
|
||||
<lastmod>2017-01-12</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
|
||||
<url>
|
||||
<loc>https://response.spearhead.systems/training/glossary/</loc>
|
||||
<lastmod>2017-01-11</lastmod>
|
||||
<lastmod>2017-01-12</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
|
||||
|
|
@ -122,7 +122,7 @@
|
|||
|
||||
<url>
|
||||
<loc>https://response.spearhead.systems/about/</loc>
|
||||
<lastmod>2017-01-11</lastmod>
|
||||
<lastmod>2017-01-12</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue