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: wiki/Alerts-and-Us.md
+14-14Lines changed: 14 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -157,9 +157,9 @@ Uptime will calculate the total downtime for the alert
157
157
| February 2024 | 0s |
158
158
| March 2024 | 0s |
159
159
| April 2024 | 1h 47m 32s |
160
-
|**May 2024**|**0s**|
161
-
| June 2024 ||
162
-
| July 2024 ||
160
+
| May 2024 |0s|
161
+
| June 2024 |0s|
162
+
|**July 2024**|**0s**|
163
163
| August 2024 ||
164
164
| September 2024 ||
165
165
| October 2024 ||
@@ -191,9 +191,9 @@ Uptime will calculate the total downtime for the alert
191
191
| February 2024 | 0s |
192
192
| March 2024 | 14m 5s |
193
193
| April 2024 | 2h 27m 56s |
194
-
|**May 2024**|**1h 57m 22s**|
195
-
| June 2024 ||
196
-
| July 2024 ||
194
+
| May 2024 | 1h 57m 22s |
195
+
| June 2024 |0s|
196
+
|**July 2024**|**0s**|
197
197
| August 2024 ||
198
198
| September 2024 ||
199
199
| October 2024 ||
@@ -227,8 +227,8 @@ Uptime will calculate the total downtime for the alert
227
227
| March | 2 | 24s | 7m 2s | Idir monitoring check failed March 21 and 22. Communicated it to IDP partner. |
228
228
| April | 3 | 2m 25s | 1h 25m 10s | Uptime was having time out issues on the 20th, could not reproduce even in uptime, suspect false alarm |
229
229
| May | 16 | 5m 26s | 7m 19s | All related to the IDIR check failing, outage communitated to the IDP partner. |
230
-
| June |||||
231
-
| July |||||
230
+
| June |0|NA|NA|NA|
231
+
| July |0|NA|NA|NA|
232
232
| August |||||
233
233
| September |||||
234
234
| October |||||
@@ -245,8 +245,8 @@ Uptime will calculate the total downtime for the alert
245
245
| March | 0 | NA | NA | NA |
246
246
| April | 2 | 3m 53s | 6m 29s | The filesystem alerts on production showed that the pods were filling up. No outage was caused, likely and internal keycloak clean up process. |
247
247
| May | 1 | 18s | 1m 0s | Elevated CPU May 29 during prod roll out, expected, No outage |
248
-
| June |||||
249
-
| July |||||
248
+
| June |0|NA|NA|NA|
249
+
| July |0|NA|NA|NA|
250
250
| August |||||
251
251
| September |||||
252
252
| October |||||
@@ -263,8 +263,8 @@ Pathfinder Team commits to acknowledging issue within 15 -30 mins and resolving
263
263
| March | 0 | NA | NA | NA |
264
264
| April | 9 | 1m 24s | 57m 57s |Uptime was having time out issues on the 20th and 25th, could not reproduce even in uptime, suspect false alarm |
265
265
| May | 19 | 4m 39s | 9m 25s | All related to the dev and test IDIR check failing, outage communitated to the IDP partner. |
266
-
| June |||||
267
-
| July |||||
266
+
| June |0|NA|NA|NA|
267
+
| July |0|NA|NA|NA|
268
268
| August |||||
269
269
| September |||||
270
270
| October |||||
@@ -281,8 +281,8 @@ Pathfinder Team commits to acknowledging issue within 15 -30 mins and resolving
281
281
| March | 0 | NA | NA | NA |
282
282
| April | 3 | 7m 3s | 12m 19s | The filesystem alerts on production showed that the pods were filling up. No outage was caused, likely and internal keycloak clean up process. |
283
283
| May | 11 | 3m 7s | 6m 18 | Minor PVC alerts about storage capacity and some CPU alerts triggered during roll outs of prod |
284
-
| June |||||
285
-
| July |||||
284
+
| June |5|1m 36s | 1m 49s | All on june 11 and 12 All due to low level PVC storage warnings 60% full. No impact on system stability|
0 commit comments