20 newincidentsReleaserollbackNo oneknows howmetric isemittedNoFlyZoneOOMSDPbypassCustomer-facingRCAAzSysLockAlbussev0sev1sev2Probablyit's anetworkingglitchNoresponseafter 7daysActualbug100 retryclicks onfailedenvironmentNightphonecallYou'vegotRA'd"Why Isee logs,but notmetrics?"MisroutedincidentSCDsev 2, butno one onthe bridgeSAWdoesn'tworkNo input= nooutput20 newincidentsReleaserollbackNo oneknows howmetric isemittedNoFlyZoneOOMSDPbypassCustomer-facingRCAAzSysLockAlbussev0sev1sev2Probablyit's anetworkingglitchNoresponseafter 7daysActualbug100 retryclicks onfailedenvironmentNightphonecallYou'vegotRA'd"Why Isee logs,but notmetrics?"MisroutedincidentSCDsev 2, butno one onthe bridgeSAWdoesn'tworkNo input= nooutput

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