Father. Husband. Problem Solver. Software Engineer.
The last post ended with an alert that pages me. That’s only useful if I know what to do when it goes off, and if the team learns something once it’s over. Those are two different documents, read at two different times: a runbook and a postmortem.
Last time I wrote down what an SLI, an SLO, and an error budget are. An SLO doesn’t do anything on its own, though. Something has to watch the budget and tell you when you’re burning through it too fast. That’s a burn-rate alert, and the part that took me the longest to get was where the time window comes in.
I’ve been working through Google’s SRE book and its companion, the SRE Workbook, and the first thing they make you do is get three terms straight: SLI, SLO, and error budget. I kept mixing them up. I’m keeping a notebook of diagrams on paper for myself, but I figured the short version belongs here too, with numbers from stuff I actually run at home.
The last post ended with an alert that pages me. That’s only useful if I know what to do when it goes off, and if the team learns something once it’s over. Those are two different documents, read at two different times: a runbook and a postmortem.
Last time I wrote down what an SLI, an SLO, and an error budget are. An SLO doesn’t do anything on its own, though. Something has to watch the budget and tell you when you’re burning through it too fast. That’s a burn-rate alert, and the part that took me the longest to get was where the time window comes in.
I’ve been working through Google’s SRE book and its companion, the SRE Workbook, and the first thing they make you do is get three terms straight: SLI, SLO, and error budget. I kept mixing them up. I’m keeping a notebook of diagrams on paper for myself, but I figured the short version belongs here too, with numbers from stuff I actually run at home.
The last post ended with an alert that pages me. That’s only useful if I know what to do when it goes off, and if the team learns something once it’s over. Those are two different documents, read at two different times: a runbook and a postmortem.
Last time I wrote down what an SLI, an SLO, and an error budget are. An SLO doesn’t do anything on its own, though. Something has to watch the budget and tell you when you’re burning through it too fast. That’s a burn-rate alert, and the part that took me the longest to get was where the time window comes in.
I’ve been working through Google’s SRE book and its companion, the SRE Workbook, and the first thing they make you do is get three terms straight: SLI, SLO, and error budget. I kept mixing them up. I’m keeping a notebook of diagrams on paper for myself, but I figured the short version belongs here too, with numbers from stuff I actually run at home.
The last post ended with an alert that pages me. That’s only useful if I know what to do when it goes off, and if the team learns something once it’s over. Those are two different documents, read at two different times: a runbook and a postmortem.
Last time I wrote down what an SLI, an SLO, and an error budget are. An SLO doesn’t do anything on its own, though. Something has to watch the budget and tell you when you’re burning through it too fast. That’s a burn-rate alert, and the part that took me the longest to get was where the time window comes in.
I’ve been working through Google’s SRE book and its companion, the SRE Workbook, and the first thing they make you do is get three terms straight: SLI, SLO, and error budget. I kept mixing them up. I’m keeping a notebook of diagrams on paper for myself, but I figured the short version belongs here too, with numbers from stuff I actually run at home.
The last post ended with an alert that pages me. That’s only useful if I know what to do when it goes off, and if the team learns something once it’s over. Those are two different documents, read at two different times: a runbook and a postmortem.
Last time I wrote down what an SLI, an SLO, and an error budget are. An SLO doesn’t do anything on its own, though. Something has to watch the budget and tell you when you’re burning through it too fast. That’s a burn-rate alert, and the part that took me the longest to get was where the time window comes in.
I’ve been working through Google’s SRE book and its companion, the SRE Workbook, and the first thing they make you do is get three terms straight: SLI, SLO, and error budget. I kept mixing them up. I’m keeping a notebook of diagrams on paper for myself, but I figured the short version belongs here too, with numbers from stuff I actually run at home.
The last post ended with an alert that pages me. That’s only useful if I know what to do when it goes off, and if the team learns something once it’s over. Those are two different documents, read at two different times: a runbook and a postmortem.
Last time I wrote down what an SLI, an SLO, and an error budget are. An SLO doesn’t do anything on its own, though. Something has to watch the budget and tell you when you’re burning through it too fast. That’s a burn-rate alert, and the part that took me the longest to get was where the time window comes in.
I’ve been working through Google’s SRE book and its companion, the SRE Workbook, and the first thing they make you do is get three terms straight: SLI, SLO, and error budget. I kept mixing them up. I’m keeping a notebook of diagrams on paper for myself, but I figured the short version belongs here too, with numbers from stuff I actually run at home.
The last post ended with an alert that pages me. That’s only useful if I know what to do when it goes off, and if the team learns something once it’s over. Those are two different documents, read at two different times: a runbook and a postmortem.
Last time I wrote down what an SLI, an SLO, and an error budget are. An SLO doesn’t do anything on its own, though. Something has to watch the budget and tell you when you’re burning through it too fast. That’s a burn-rate alert, and the part that took me the longest to get was where the time window comes in.
I’ve been working through Google’s SRE book and its companion, the SRE Workbook, and the first thing they make you do is get three terms straight: SLI, SLO, and error budget. I kept mixing them up. I’m keeping a notebook of diagrams on paper for myself, but I figured the short version belongs here too, with numbers from stuff I actually run at home.
The last post ended with an alert that pages me. That’s only useful if I know what to do when it goes off, and if the team learns something once it’s over. Those are two different documents, read at two different times: a runbook and a postmortem.
Last time I wrote down what an SLI, an SLO, and an error budget are. An SLO doesn’t do anything on its own, though. Something has to watch the budget and tell you when you’re burning through it too fast. That’s a burn-rate alert, and the part that took me the longest to get was where the time window comes in.
I’ve been working through Google’s SRE book and its companion, the SRE Workbook, and the first thing they make you do is get three terms straight: SLI, SLO, and error budget. I kept mixing them up. I’m keeping a notebook of diagrams on paper for myself, but I figured the short version belongs here too, with numbers from stuff I actually run at home.
The last post ended with an alert that pages me. That’s only useful if I know what to do when it goes off, and if the team learns something once it’s over. Those are two different documents, read at two different times: a runbook and a postmortem.
Last time I wrote down what an SLI, an SLO, and an error budget are. An SLO doesn’t do anything on its own, though. Something has to watch the budget and tell you when you’re burning through it too fast. That’s a burn-rate alert, and the part that took me the longest to get was where the time window comes in.
I’ve been working through Google’s SRE book and its companion, the SRE Workbook, and the first thing they make you do is get three terms straight: SLI, SLO, and error budget. I kept mixing them up. I’m keeping a notebook of diagrams on paper for myself, but I figured the short version belongs here too, with numbers from stuff I actually run at home.
The last post ended with an alert that pages me. That’s only useful if I know what to do when it goes off, and if the team learns something once it’s over. Those are two different documents, read at two different times: a runbook and a postmortem.
Last time I wrote down what an SLI, an SLO, and an error budget are. An SLO doesn’t do anything on its own, though. Something has to watch the budget and tell you when you’re burning through it too fast. That’s a burn-rate alert, and the part that took me the longest to get was where the time window comes in.
I’ve been working through Google’s SRE book and its companion, the SRE Workbook, and the first thing they make you do is get three terms straight: SLI, SLO, and error budget. I kept mixing them up. I’m keeping a notebook of diagrams on paper for myself, but I figured the short version belongs here too, with numbers from stuff I actually run at home.