20 newincidentsSCDsev2NightphonecallAzSysLocksev0OOMAlbussev 2, butno one onthe bridgeYou'vegotRA'd100 retryclicks onfailedenvironmentCustomer-facingRCAProbablyit's anetworkingglitchNo input= nooutput"Why Isee logs,but notmetrics?"SAWdoesn'tworkActualbugReleaserollbackMisroutedincidentNo oneknows howmetric isemittedNoFlyZoneNoresponseafter 7daysSDPbypasssev120 newincidentsSCDsev2NightphonecallAzSysLocksev0OOMAlbussev 2, butno one onthe bridgeYou'vegotRA'd100 retryclicks onfailedenvironmentCustomer-facingRCAProbablyit's anetworkingglitchNo input= nooutput"Why Isee logs,but notmetrics?"SAWdoesn'tworkActualbugReleaserollbackMisroutedincidentNo oneknows howmetric isemittedNoFlyZoneNoresponseafter 7daysSDPbypasssev1

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