NightphonecallNo input= nooutputProbablyit's anetworkingglitchSCDNoresponseafter 7daysAzSysLockAlbusSAWdoesn'tworkCustomer-facingRCANo oneknows howmetric isemittedsev 2, butno one onthe bridgeMisroutedincidentsev0ReleaserollbackNoFlyZoneOOMsev220 newincidentsActualbugYou'vegotRA'd"Why Isee logs,but notmetrics?"SDPbypasssev1100 retryclicks onfailedenvironmentNightphonecallNo input= nooutputProbablyit's anetworkingglitchSCDNoresponseafter 7daysAzSysLockAlbusSAWdoesn'tworkCustomer-facingRCANo oneknows howmetric isemittedsev 2, butno one onthe bridgeMisroutedincidentsev0ReleaserollbackNoFlyZoneOOMsev220 newincidentsActualbugYou'vegotRA'd"Why Isee logs,but notmetrics?"SDPbypasssev1100 retryclicks onfailedenvironment

DRI Bingo - Call List

(Print) Use this randomly generated list as your call list when playing the game. There is no need to say the BINGO column name. Place some kind of mark (like an X, a checkmark, a dot, tally mark, etc) on each cell as you announce it, to keep track. You can also cut out each item, place them in a bag and pull words from the bag.


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
  1. Night phone call
  2. No input = no output
  3. Probably it's a networking glitch
  4. SCD
  5. No response after 7 days
  6. AzSysLock
  7. Albus
  8. SAW doesn't work
  9. Customer-facing RCA
  10. No one knows how metric is emitted
  11. sev 2, but no one on the bridge
  12. Misrouted incident
  13. sev 0
  14. Release rollback
  15. NoFlyZone
  16. OOM
  17. sev 2
  18. 20 new incidents
  19. Actual bug
  20. You've got RA'd
  21. "Why I see logs, but not metrics?"
  22. SDP bypass
  23. sev 1
  24. 100 retry clicks on failed environment