OOMSDPbypassActualbugsev1ReleaserollbackYou'vegotRA'dsev2Probablyit's anetworkingglitchNightphonecall100 retryclicks onfailedenvironmentsev 2, butno one onthe bridge"Why Isee logs,but notmetrics?"SAWdoesn'tworkNo oneknows howmetric isemittedNoFlyZone20 newincidentsNoresponseafter 7daysAzSysLocksev0SCDMisroutedincidentCustomer-facingRCANo input= nooutputAlbusOOMSDPbypassActualbugsev1ReleaserollbackYou'vegotRA'dsev2Probablyit's anetworkingglitchNightphonecall100 retryclicks onfailedenvironmentsev 2, butno one onthe bridge"Why Isee logs,but notmetrics?"SAWdoesn'tworkNo oneknows howmetric isemittedNoFlyZone20 newincidentsNoresponseafter 7daysAzSysLocksev0SCDMisroutedincidentCustomer-facingRCANo input= nooutputAlbus

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