Incident and event response
I’m going to put Murphy’s Law here again because I cannot state this enough:
Dealing with incident and event response involves either a lot of work or zero work. It depends on how prepared you are and how unique the incident or event is. Incident and event response covers a lot of ground from automation and cost control, to cybersecurity.
How a DevOps engineer responds to an event depends on a great number of things. In terms of dealing with clients and customers, a Service Level Objective (SLO) is used when a response is necessary. However, this is largely on production environments and requires the definition of a Service Level Indicator (SLI). It also involves the creation of an error budget to determine the right time to add new features and what the right time is to work on the maintenance of a system. Lower-priority development environments are used to stress...