Process for companies that can’t afford to create it from the ground up, based on best practices: transparency, trust, and communication.
Think incidents cost you a lot?
Try not having a process in place.
Fits in with your tools: Get alerted by PagerDuty, open an incident in Slack, tie in data from your CI and Version Control systems, and create a Ticket to make sure the appropriate fixes actually get done.
Automate the logistical toil of running an incident response process — Slack commands and APIs, not Google Docs and random emails.
Incident response that aligns with your values: transparency, auditability, and trust
Incident response should be transparent and auditable. FireHydrant provides metrics on response handling, PDF postmortem reports for appropriate stakeholders, and more to improve organizational confidence and trust.
Created by engineers with years of SRE experience — FireHydrant is a cutting edge tool you can trust, based on knowledge and research, not fads and false promises.
Close the loop on incident response. FireHydrant’s processes promote accountability and follow-through so incidents are less frequent and impactful.
The key to good incident response is communication: before, during, and a fter an incident.
Document the complex relationships between individual roles, teams, apps, and servers that are too often in people’s heads or in random documents.
Route the right information to the right people, and help them get up to speed as quickly as possible.
Create immutable documentation of incidents, responses, communication, and more to decentralize, standardize, and improve historical knowledge of deploys, incidents, responses, and more