{"id":27288,"date":"2017-02-02T03:07:49","date_gmt":"2017-02-02T01:07:49","guid":{"rendered":"https:\/\/mamchenkov.net\/wordpress\/?p=27288"},"modified":"2017-02-02T03:07:49","modified_gmt":"2017-02-02T01:07:49","slug":"pagerduty-incident-response-documentation","status":"publish","type":"post","link":"https:\/\/mamchenkov.net\/wordpress\/2017\/02\/02\/pagerduty-incident-response-documentation\/","title":{"rendered":"PagerDuty Incident Response Documentation"},"content":{"rendered":"\n

PagerDuty<\/a> shares their Incident Response Documentation<\/a>:<\/p>\n

This documentation covers parts of the PagerDuty Incident Response process. It is a cut-down version of our internal documentation, used at PagerDuty for any major incidents, and to prepare new employees for on-call responsibilities. It provides information not only on preparing for an incident, but also what to do during and after. It is intended to be used by on-call practitioners and those involved in an operational incident response process (or those wishing to enact a formal incident response process).<\/p><\/blockquote>\n

I think this is a goldmine for anybody involved with incident response teams, operations, monitoring, technical support, network centers, and other similar setups. \u00a0Not only it covers the specific steps and expectations during different situations, but it also defines the culture, which the company is trying to built.<\/p>\n

I wish I had this 15 years ago when I was involved in setting up the Network Operations Center (NOC). \u00a0I will definitely use it in the near future, when we’ll be setting up the support department at work.<\/p>\n\n","protected":false},"excerpt":{"rendered":"\n

PagerDuty shares their Incident Response Documentation: This documentation covers parts of the PagerDuty Incident Response process. It is a cut-down version of our internal documentation, used at PagerDuty for any major incidents, and to prepare new employees for on-call responsibilities. It provides information not only on preparing for an incident, but also what to do … Continue reading PagerDuty Incident Response Documentation<\/span><\/a><\/p>\n\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"PagerDuty Incident Response Documentation #SysAdmin #DevOps #monitoring #support","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"_links_to":"","_links_to_target":""},"categories":[1,133,62],"tags":[3069,78,127,3491],"keyring_services":[],"class_list":["post-27288","post","type-post","status-publish","format-standard","hentry","category-general","category-sysadmin","category-technology","tag-best-practices","tag-documentation","tag-monitoring","tag-pagerduty"],"aioseo_notices":[],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack-related-posts":[{"id":27346,"url":"https:\/\/mamchenkov.net\/wordpress\/2017\/02\/12\/incident-pit\/","url_meta":{"origin":27288,"position":0},"title":"Incident pit","author":"Leonid Mamchenkov","date":"February 12, 2017","format":false,"excerpt":"I came across the Wikipedia page for incident pit, which was a concept derived from analyzing multiple incident reports in diving: The diagram shown is something that has evolved from studying many incident reports. It is important to realize that the shape of the \"Pit\" is in no way connected\u2026","rel":"","context":"In "All"","block_context":{"text":"All","link":"https:\/\/mamchenkov.net\/wordpress\/category\/general\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/mamchenkov.net\/wordpress\/wp-content\/uploads\/2017\/02\/incident-pit-500x354.jpg?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]},{"id":28538,"url":"https:\/\/mamchenkov.net\/wordpress\/2018\/05\/02\/code-quality-tools-in-php-to-check-and-improve-your-code\/","url_meta":{"origin":27288,"position":1},"title":"Code quality tools in PHP to check and improve your code","author":"Leonid Mamchenkov","date":"May 2, 2018","format":false,"excerpt":"\"Code quality tools in PHP to check and improve your code\" is a list of both some very well known tools and some new kids on the block.\u00a0 The article covers the following: PHP-CS-Fixer Documentation Github PHPCS Documentation Github PHPMD Documenation Official website PHPStan Github PHPUnit Documentation Github PHPLoc Github\u2026","rel":"","context":"In "All"","block_context":{"text":"All","link":"https:\/\/mamchenkov.net\/wordpress\/category\/general\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":28082,"url":"https:\/\/mamchenkov.net\/wordpress\/2017\/10\/12\/google-developer-documentation-style-guide\/","url_meta":{"origin":27288,"position":2},"title":"Google Developer Documentation Style Guide","author":"Leonid Mamchenkov","date":"October 12, 2017","format":false,"excerpt":"\"Google Developer Documentation Style Guide\" is a guide for Google developers on how to write the developer documentation.\u00a0 As someone who have been involved in technical documentation for years now, I find a general lack of such guides from other companies interesting and slightly disturbing. Kudos to Google for the\u2026","rel":"","context":"In "All"","block_context":{"text":"All","link":"https:\/\/mamchenkov.net\/wordpress\/category\/general\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":37915,"url":"https:\/\/mamchenkov.net\/wordpress\/2019\/03\/11\/gitguardian-api-security-best-practices\/","url_meta":{"origin":27288,"position":3},"title":"GitGuardian API Security Best Practices","author":"Leonid Mamchenkov","date":"March 11, 2019","format":false,"excerpt":"The team behind GitGuardian, a tool that helps developers to keep credentials and other secrets outside of the source code, shares their documentation for the API security best practices. The cool bit about their documentation is that it covers both how to avoid the issues and how to solve them\u2026","rel":"","context":"In "All"","block_context":{"text":"All","link":"https:\/\/mamchenkov.net\/wordpress\/category\/general\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":28376,"url":"https:\/\/mamchenkov.net\/wordpress\/2018\/02\/11\/zeal-vim-offline-cakephp-and-other-documentation\/","url_meta":{"origin":27288,"position":4},"title":"Zeal + Vim = offline CakePHP (and other) documentation","author":"Leonid Mamchenkov","date":"February 11, 2018","format":false,"excerpt":"As any long time Vim user, I'm constantly looking for ways to tweak and improve my text editor configuration, and make me even more efficient.\u00a0 Today, I came across a very handy addition - Zeal\u00a0- an offline documentation browser for developers. (Thanks to this blog post, which also mentions Dash\u2026","rel":"","context":"In "All"","block_context":{"text":"All","link":"https:\/\/mamchenkov.net\/wordpress\/category\/general\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/mamchenkov.net\/wordpress\/wp-content\/uploads\/2018\/02\/Zeal-CakePHP-Inflector-500x265.png?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]},{"id":19709,"url":"https:\/\/mamchenkov.net\/wordpress\/2014\/01\/21\/devdocs-io-a-local-cache-of-searchable-documentation\/","url_meta":{"origin":27288,"position":5},"title":"DevDocs.io – a local cache of searchable documentation","author":"Leonid Mamchenkov","date":"January 21, 2014","format":"link","excerpt":"DevDocs.io - a local cache of searchable documentation I've heard about this project for a while now, but tried it only today. \u00a0This blog post left me no options. \u00a0And I'm glad. \u00a0Because DevDocs are absolutely awesome!","rel":"","context":"In "All"","block_context":{"text":"All","link":"https:\/\/mamchenkov.net\/wordpress\/category\/general\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"jetpack_sharing_enabled":true,"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/posts\/27288","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/comments?post=27288"}],"version-history":[{"count":0,"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/posts\/27288\/revisions"}],"wp:attachment":[{"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/media?parent=27288"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/categories?post=27288"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/tags?post=27288"},{"taxonomy":"keyring_services","embeddable":true,"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/keyring_services?post=27288"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}