You'vegotRA'dsev1NoFlyZoneActualbugsev0AlbusCustomer-facingRCAReleaserollbackNo oneknows howmetric isemittedOOMsev2AzSysLockSDPbypass20 newincidentsMisroutedincidentProbablyit's anetworkingglitchNo input= nooutputSAWdoesn'tworkSCD"Why Isee logs,but notmetrics?"100 retryclicks onfailedenvironmentNoresponseafter 7daysNightphonecallsev 2, butno one onthe bridgeYou'vegotRA'dsev1NoFlyZoneActualbugsev0AlbusCustomer-facingRCAReleaserollbackNo oneknows howmetric isemittedOOMsev2AzSysLockSDPbypass20 newincidentsMisroutedincidentProbablyit's anetworkingglitchNo input= nooutputSAWdoesn'tworkSCD"Why Isee logs,but notmetrics?"100 retryclicks onfailedenvironmentNoresponseafter 7daysNightphonecallsev 2, butno one onthe bridge

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