100 retryclicks onfailedenvironment"Why Isee logs,but notmetrics?"sev1You'vegotRA'dNightphonecallActualbugNoresponseafter 7daysSDPbypasssev2OOMProbablyit's anetworkingglitchSCD20 newincidentsNoFlyZoneMisroutedincidentAzSysLocksev0No oneknows howmetric isemittedAlbusNo input= nooutputReleaserollbackCustomer-facingRCAsev 2, butno one onthe bridgeSAWdoesn'twork100 retryclicks onfailedenvironment"Why Isee logs,but notmetrics?"sev1You'vegotRA'dNightphonecallActualbugNoresponseafter 7daysSDPbypasssev2OOMProbablyit's anetworkingglitchSCD20 newincidentsNoFlyZoneMisroutedincidentAzSysLocksev0No oneknows howmetric isemittedAlbusNo input= nooutputReleaserollbackCustomer-facingRCAsev 2, butno one onthe bridgeSAWdoesn'twork

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