-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.html
425 lines (405 loc) · 16.3 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
<!doctype html>
<html lang="en">
<head>
<meta charset="UTF-8"/>
<meta name="viewport" content="width=device-width, initial-scale=1.0"/>
<title>Incident Adventures</title>
<link rel="icon" href="/favicon.svg" type="image/svg+xml" sizes="any">
<meta name="title" content="Incident Adventures">
<meta name="description" content="Incident Adventures is an easy way to run simulated incidents and responses for your engineering team. Set up scenarios and let your team discover the root cause while learning about what to do along the way.">
<!-- Open Graph / Facebook -->
<meta property="og:type" content="website">
<meta property="og:url" content="https://www.incidentadventures.com">
<meta property="og:title" content="Incident Adventures">
<meta property="og:description" content="Incident Adventures is an easy way to run simulated incidents and responses for your engineering team. Set up scenarios and let your team discover the root cause while learning about what to do along the way.">
<meta property="og:image" content="c">
<!-- Twitter -->
<meta property="twitter:card" content="summary_large_image">
<meta property="twitter:url" content="https://www.incidentadventures.com">
<meta property="twitter:title" content="Incident Adventures">
<meta property="twitter:description" content="Incident Adventures is an easy way to run simulated incidents and responses for your engineering team. Set up scenarios and let your team discover the root cause while learning about what to do along the way.">
<meta property="twitter:image" content="https://www.incidentadventures.com/og.png">
<style>
/*! Thanks to normalize.css v8.0.1 | MIT License | github.com/necolas/normalize.css */
html {
line-height: 1.3;
-webkit-text-size-adjust: 100%;
font-size: max(6px, min(10px, 1vw));
}
body {
margin: 0;
}
h1 {
font-size: min(10vw, 11rem);
margin: 0.67em 0;
}
h2 {
font-size: min(6vw, 6.5rem);
margin: 0.67em 0;
}
h3 {
font-size: 5rem;
margin: 0.67em 0;
}
h4 {
font-size: 3.375rem;
margin: 0.67em 0;
}
p, li {
font-size: 2.25rem;
}
hr {
box-sizing: content-box;
height: 0;
overflow: visible;
}
pre {
font-family: monospace, monospace;
font-size: 1em;
}
b, strong {
font-weight: bolder;
}
code, kbd, samp {
font-family: monospace, monospace;
font-size: 1em;
}
:root {
--bg: #011627;
--fg: #C9EDDC;
--separator: #388697;
--alt-bg: #EC4E20;
--alt-fg: #011627;
--max-width: 1200px;
}
body {
font-family: Consolas,monaco,monospace;
background-color: var(--bg);
color: var(--fg);
margin: 0;
padding: 0;
}
header {
padding: min(12rem, 20vw) 2rem;
background: var(--bg);
}
section:nth-of-type(even) {
padding-top: 34px;
padding-bottom: 34px;
}
section:nth-of-type(odd) {
background: var(--alt-bg);
color: var(--alt-fg);
position: relative;
z-index: 1;
}
section:nth-of-type(odd) > .content {
padding-top: 40px;
padding-bottom: 40px;
}
section:nth-of-type(even) > .content {
background: var(--alt-fg);
padding-top: 6px;
padding-bottom: 6px;
}
.content {
position: relative;
z-index: 20;
max-width: var(--max-width);
margin-left: auto;
margin-right: auto;
background: inherit;
padding: 0 min(10px, 10vw);
}
section > ol {
padding-left: 120px;
}
footer {
text-align: center;
padding: 6px;
margin: 14px;
background-color: var(--bg);
z-index: 20;
position: relative;
}
a, a:visited {
color: inherit;
}
.wave-container {
max-width: var(--max-width);
}
.wave-left, .wave-right {
filter: blur(3px);
position: fixed;
height: 100vh;
z-index: 1;
}
.wave {
height: 100vh;
}
.wave-left {
left: 0;
}
.wave-left > .wave {
background: var(--fg);
}
.wave-right {
right: 0;
z-index: 2;
}
.wave-right > .wave {
background: var(--bg);
}
/* Thanks to https://css-generators.com/wavy-shapes/ */
.wave-left > .wave {
--mask: radial-gradient(100px at calc(100% + 57px) 50%,#0000 calc(99% - 10px),#000 calc(101% - 10px) 99%,#0000 101%) calc(50% - 43px + .5px) calc(50% - 152px)/ 86px 304px repeat-y,
radial-gradient(100px at -57px 50%,#0000 calc(99% - 10px),#000 calc(101% - 10px) 99%,#0000 101%) calc(50% + 43px) 50%/86px 304px repeat-y;
-webkit-mask: var(--mask);
mask: var(--mask);
min-width: 86px;
width: 20vw;
}
@media (width >= 400px) {
section:nth-of-type(odd) {
padding-right: min(22vw, 300px);
}
section:nth-of-type(even) {
padding-left: min(22vw, 300px);
}
.wave-right > .wave {
--mask: radial-gradient(100px at calc(100% + 57px) 50%,#0000 calc(99% - 10px),#000 calc(101% - 10px) 99%,#0000 101%) calc(50% - 43px + .5px) calc(50% - 152px)/ 86px 304px repeat-y,
radial-gradient(100px at -57px 50%,#0000 calc(99% - 10px),#000 calc(101% - 10px) 99%,#0000 101%) calc(50% + 43px) 50%/86px 304px repeat-y;
-webkit-mask: var(--mask);
mask: var(--mask);
min-width: 86px;
width: 20vw;
}
}
@media (width >= 950px) {
.wave-left > .wave {
--mask: radial-gradient(200px at calc(100% + 114px) 50%,#0000 calc(99% - 20px),#000 calc(101% - 20px) 99%,#0000 101%) calc(50% - 86px + .5px) calc(50% - 304px)/ 172px 608px repeat-y,
radial-gradient(200px at -114px 50%,#0000 calc(99% - 20px),#000 calc(101% - 20px) 99%,#0000 101%) calc(50% + 86px) 50%/172px 608px repeat-y;
-webkit-mask: var(--mask);
mask: var(--mask);
min-width: 186px;
width: 20vw;
}
.wave-right > .wave {
--mask: radial-gradient(200px at calc(100% + 114px) 50%,#0000 calc(99% - 20px),#000 calc(101% - 20px) 99%,#0000 101%) calc(50% - 86px + .5px) calc(50% - 304px)/ 172px 608px repeat-y,
radial-gradient(200px at -114px 50%,#0000 calc(99% - 20px),#000 calc(101% - 20px) 99%,#0000 101%) calc(50% + 86px) 50%/172px 608px repeat-y;
-webkit-mask: var(--mask);
mask: var(--mask);
min-width: 186px;
width: 20vw;
}
}
.flex {
display: flex;
justify-content: center;
align-items: center;
}
.circle::before {
content: "";
position: absolute;
left: 0;
top: 50%;
transform: translateY(-50%);
width: 1em;
height: 1em;
background: var(--fg);
border-radius: 50%;
}
.circle {
position: relative;
z-index: 10;
line-height: 1;
padding-left: 1.1em;
flex: 0;
background: var(--bg);
background: radial-gradient(circle, rgba(1,22,39,1) 30%, rgba(0,0,0,0) 70%);
}
</style>
</head>
<body>
<div class="wave-container">
<div class="wave-left"><div class="wave"></div></div>
<div class="wave-right"><div class="wave"></div></div>
</div>
<header>
<div class="flex">
<h1 class="circle">Incident Adventures</h1>
</div>
</header>
<section>
<div class="content">
<h2>Incidents Happen</h2>
<p>
Are you prepared for an incident? What will your team actually do when PagerDuty calls? Be prepared with
Incident Adventures, the latest way to have fun and get prepared for when the worst happens.
</p>
<p>
Inspired by
<a href="https://www.escapethispodcast.com" target="_blank">Escape this Podcast</a> and role playing games,
Incident Adventures is an easy way to run simulated incidents and responses for your engineering team.
Set up scenarios and let your team discover the root cause while learning about what to do along the way.
</p>
</div>
</section>
<section>
<div class="content">
<h2>Imagination Over Simulations</h2>
<p>
Incident Adventures are simulated by an Adventure Master (or GM/DM for the tabletop players). Each scenario
takes place by doing as much as possible in real life, but as the practice Response Team explores the
graphs,
logs, and data the Adventure Master will let the team know when they “see” something different. For example,
if
the scenario’s root cause is that an SSL certificate has expired, the team goes and looks at the production
graph for 200’s, the Adventure Master might tell the team that while the chart looks normal in reality, in
the
scenario, the rate is noticeably lower in the scenario.
</p>
<p>
By using the imagination to simulate, the team exploring the scenario can go look at anything anywhere and
the
Adventure Master merely needs to be able to tell the team what it would look like as the Adventure Master
knows
the root cause.
</p>
</div>
</section>
<section>
<div class="content">
<h2>How It Works</h2>
<h3>Preparation</h3>
<p>
While not much is needed to run an Incident Adventure, some preparation is required.
</p>
<h4>1. Collect a list of root causes</h4>
<p>
You don’t need very many, and they don’t need to be super complex, but it is a good idea to have root causes
in various parts of your infrastructure or code. That way each root cause scenario can introduce or refresh
the team about that part of your system.
</p>
<h4>2. Preparing to run the scenario</h4>
<p>
The Adventure Master running the scenario needs to be knowledgeable enough to know when and how a given root
cause would express into whatever the team is exploring. In addition, the Adventure Master or perhaps a
helper needs to be able to step in and provide hints or direction if the team is running into a wall.
</p>
<p>
Remember: This is about learning and practicing what to do in an incident. Being stuck for too long is not
only frustrating, but also hinders the goal of learning.
</p>
<h4>3. Practice Response Team Size</h4>
<p>
A practice Response Team should be 2-3 people of about the same level of ability. If you have a team that is
unbalanced, let the senior team member know that they should give their junior time to think and respond
first.
</p>
<p>
It is also possible to have some observers, but observers should be for learning the basics. You don’t want
to give observers a false sense of ability. Observers will also increase the pressure, so get permission and
senior team members.
</p>
<h4>4. Time Length</h4>
<p>
Scenarios should take between 30 and 60 minutes. Two, 30 minute scenarios or a single 45-60 minute scenario
is about all that single session should try to do. More than that could be information overload for the
team.
</p>
</div>
</section>
<section>
<div class="content">
<h3>Getting Started</h3>
<p>
You have a practice Response Team and your selected root cause, so time to get started with the rules!
Here’s a suggested introduction:
</p>
<p>
Welcome to Incident Adventures! In just a moment an alert will go off, but first let me set some ground
rules.
</p>
<ol>
<li>Talk through what you are doing and what you are looking at. Share your screen if possible.</li>
<li>
I am your filter to the outside world. I will let you know if something you are looking at is different
in our scenario, but I can also be other teams and the customer.
</li>
<li>This is an open book setup. Search and use the resources you would have in a real incident.</li>
<li>We’re here to learn and have fun. I might give you some hints, but getting stuck for a bit is ok.</li>
</ol>
<h4>The Alert</h4>
<p>
Let your team know that an alert has occurred. If possible, give them the text of the issue report or
specific alert. User reports are also ok. The alert or issue should be true, but also shouldn't give much
away. For example, “increasing 400 responses” or “user reports they cannot access service” are clear
starting points, but don’t tell too much about that root cause.
</p>
</div>
</section>
<section>
<div class="content">
<h3>The Response</h3>
<p>
75% of the response work is just getting started. Just knowing where to find the Standard Operating Procedure, see
the logs, or monitoring data is a great start, but some inexperienced teams may need help with this step.
</p>
<h4>Dead Ends</h4>
<p>
A good adventure has some dead ends. Take notes on the suggested, but incorrect root causes. They might be
great future scenarios for others!
</p>
</div>
</section>
<section>
<div class="content">
<h3>Discovery and Closeout</h3>
<p>
You will have to determine when to count the root cause as found. Usually it takes two steps: the idea and
the confirmation. When the team thinks they have the root cause asking, “How would you confirm that?” is a
great way to take it out of speculation.
</p>
<h4>Solution</h4>
<p>
Once you have congratulated the team on the discovery of the root cause, some root causes may have the
option
of asking how they would resolve the issue. This might just be a discussion or having the team bring up the
runbook that would be followed.
</p>
</div>
</section>
<section>
<div class="content">
<h2>Expansions</h2>
<p>
Want more? Here are some ideas to set you up for more adventures!
</p>
<ul>
<li>Layered root causes. Why limit yourself to just one?</li>
<li>Ticking clock. Want to make it more stressful like a real incident?</li>
<li>Additional alerts. Sometimes the first alert is just the first. Having another alert go off during the
scenario can help or confuse the team.
</li>
<li>Run competing teams at a company off-site.</li>
</ul>
</div>
</section>
<section>
<div class="content">
<h2>Consulting</h2>
<p>
Want help setting up or running Incident Adventures for your company? Interested in an outside review of
your incident planning?
</p>
<p>
Contact: Wil Wade<br/> Email: <a href="mailto:[email protected]">[email protected]</a>
</p>
</div>
</section>
<footer>
<p><a href="https://creativecommons.org/licenses/by/4.0/" target="_blank">CC BY 4.0</a> Wil Wade.</p>
</footer>
</body>
</html>