You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: advent-of-calm/day-15.md
+13-1Lines changed: 13 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,6 +29,8 @@ By adding operational metadata, you transform this into queryable support docume
29
29
30
30
Unlike static wikis, this documentation lives with the architecture and stays in sync.
31
31
32
+
Side-note: at the moment we are putting a lot of information into the `metadata` section, but there are some more advanced techniques that we won't discuss here but can be used to do this in a more structured way.
33
+
32
34
### 2. Add Operational Metadata to Nodes
33
35
34
36
Enrich your key services with support information.
@@ -222,6 +224,16 @@ Generate an incident summary based on my architecture:
222
224
6. Follow-up actions to prevent recurrence
223
225
```
224
226
227
+
228
+
Let's keep that for the future:
229
+
230
+
```
231
+
Capture the incident report you just created as a markdown document in `docs/load-balancer-incident-report.md`.
232
+
```
233
+
234
+
To think about: Did you get exactly the same content as when it first generated? Does it depend on which model you used? Does it matter?
235
+
236
+
225
237
### 11. Compare: Wiki vs Architecture-as-Documentation
226
238
227
239
| Aspect | Traditional Wiki | CALM Architecture |
@@ -236,7 +248,7 @@ Generate an incident summary based on my architecture:
0 commit comments