About
This site documents parts of the Elimu Informatics Incident Response process. It is a cut-down version of our internal documentation, used at Elimu Informatics 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.
Few companies seem to talk about their internal processes for dealing with major incidents. We would like to change that by opening up our documentation to the community, in the hopes that it proves useful to others who may want to formalize their own processes. Additionally, it provides an opportunity for others to suggest improvements, which ends up helping everyone.
What is this?#
A collection of pages detailing how to efficiently deal with any major incidents that might arise, along with information on how to go on-call effectively. It provides lessons learned the hard way, along with training material for getting you up to speed quickly.
Who is this for?#
It is intended for on-call practitioners and those involved in an operational incident response process, or those wishing to enact a formal incident response process.
Why do I need it?#
Incident response is something you hope to never need, but when you do, you want it to go smoothly and seamlessly. Normally the knowledge of how to handle incidents within your company will be built up over time, getting better with each incident.
What is covered?#
Anything from preparing to go on-call, definitions of severities, incident call etiquette, all the way to how to run a post-mortem, and providing our post-mortem template. We even include our security incident response process.
What is missing?#
This isn't an exact clone of our internal documentation, but instead has some information removed. Things such as our phone numbers, names of internal tools and systems which are not (yet) open sourced, images of our dashboards, etc. Basically anything that is specific to Elimu Informatics or is too sensitive to share.
License#
This documentation is provided under the Apache License 2.0. In plain English that means you can use and modify this documentation and use it both commercially and for private use. However, you must include any original copyright notices, and the original LICENSE file.