@hiiretail/gcp-infra-cli 0.83.1 → 0.83.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -6,27 +6,27 @@
|
|
|
6
6
|
|
|
7
7
|
**Incident end**: <!-- The date and time when the incident was resolved, for example: 2022-06-14 14.53 CET -->
|
|
8
8
|
|
|
9
|
-
**Problem statement**: <!-- Describe
|
|
9
|
+
**Problem statement**: <!-- Describe what the problem was. It is important to keep this short, one or two sentances are enough. Example: An Out of Memory error was thrown -->
|
|
10
10
|
|
|
11
11
|
**Impacted customer(s)**: <!-- What customer(s) that were affected -->
|
|
12
12
|
|
|
13
|
-
**Impact to customer**: <!-- Describe how the customer, and end customers, was affected by the incident -->
|
|
13
|
+
**Impact to customer**: <!-- Describe how the customer, and end customers, was affected by the incident. Where they completely unable to use the system? Or was there some feature that wasn't working? -->
|
|
14
14
|
|
|
15
15
|
**Ticket information**: <!-- Add link(s) to any Jira issues -->
|
|
16
16
|
|
|
17
|
-
**Services involved**: <!-- List the
|
|
17
|
+
**Services involved**: <!-- List the Hii Retail-service(s) that were involved in the incident, for example checkout-poslog -->
|
|
18
18
|
|
|
19
19
|
## Sequence of Events
|
|
20
20
|
|
|
21
21
|
<!--
|
|
22
|
-
Describe the events that caused the incident, starting from
|
|
22
|
+
Describe the events that caused the incident, starting from when the issues started up until the incident was resolved. If no alert was triggered, the first event would be when the issues first started.
|
|
23
23
|
|
|
24
24
|
Example:
|
|
25
25
|
|
|
26
|
-
2022-06-14 14.36 - Alert X was triggered
|
|
27
|
-
2022-06-14 14.36 - Team started working on the incident
|
|
28
|
-
2022-06-14 14.49 - A fix was pushed and deployed
|
|
29
|
-
2022-06-14 14.53 - Incident was resolved
|
|
26
|
+
- 2022-06-14 14.36 - Alert X was triggered
|
|
27
|
+
- 2022-06-14 14.36 - Team started working on the incident
|
|
28
|
+
- 2022-06-14 14.49 - A fix was pushed and deployed
|
|
29
|
+
- 2022-06-14 14.53 - Incident was resolved
|
|
30
30
|
-->
|
|
31
31
|
|
|
32
32
|
## Five Whys
|
|
@@ -54,22 +54,25 @@ Problem: The vehicle won't start
|
|
|
54
54
|
## Summary
|
|
55
55
|
|
|
56
56
|
<!--
|
|
57
|
-
|
|
57
|
+
This section should be written last, when all of the other bullets in the RCA has been written. The summary should include:
|
|
58
|
+
|
|
59
|
+
* What the problem statement was, what the root cause of it was and a short summary of the highest prioritized action points.
|
|
58
60
|
-->
|
|
59
61
|
|
|
60
62
|
## Action items
|
|
61
63
|
|
|
62
64
|
<!--
|
|
63
|
-
A table that describes the different actions that was the outcome of the analysis
|
|
64
|
-
|
|
65
|
+
A table that describes the different actions that was the outcome of the analysis and who is the owner of the task. The table should be in order of priority.
|
|
66
|
+
|
|
67
|
+
When creating Jira issues, add the label "RCA" to them.
|
|
65
68
|
|
|
66
69
|
Example:
|
|
67
|
-
| Description | Owner |
|
|
70
|
+
| Description | Owner | Jira issue |
|
|
68
71
|
|-------------|-------|------|--------|
|
|
69
|
-
| Create alert for high CPU Usage | Bob the Builder |
|
|
70
|
-
| | | |
|
|
72
|
+
| Create alert for high CPU Usage | Bob the Builder | HII-1234 |
|
|
73
|
+
| | | |
|
|
71
74
|
-->
|
|
72
75
|
|
|
73
|
-
| Description | Owner |
|
|
74
|
-
|
|
75
|
-
| | |
|
|
76
|
+
| Description | Owner | Jira issue |
|
|
77
|
+
|-------------|-------|------------|
|
|
78
|
+
| | | |
|