Noresponseafter 7daysAzSysLockAlbusYou'vegotRA'dSCDMisroutedincidentCustomer-facingRCAOOM100 retryclicks onfailedenvironmentsev0NoFlyZoneSDPbypasssev 2, butno one onthe bridge20 newincidentsNightphonecallSAWdoesn'tworkNo input= nooutputReleaserollback"Why Isee logs,but notmetrics?"Actualbugsev2No oneknows howmetric isemittedProbablyit's anetworkingglitchsev1Noresponseafter 7daysAzSysLockAlbusYou'vegotRA'dSCDMisroutedincidentCustomer-facingRCAOOM100 retryclicks onfailedenvironmentsev0NoFlyZoneSDPbypasssev 2, butno one onthe bridge20 newincidentsNightphonecallSAWdoesn'tworkNo input= nooutputReleaserollback"Why Isee logs,but notmetrics?"Actualbugsev2No oneknows howmetric isemittedProbablyit's anetworkingglitchsev1

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