sev 2, butno one onthe bridgesev0No input= nooutputNo oneknows howmetric isemitted"Why Isee logs,but notmetrics?"SDPbypassReleaserollbackCustomer-facingRCASCDAzSysLockAlbussev1sev2Probablyit's anetworkingglitchMisroutedincidentNoresponseafter 7daysNoFlyZone20 newincidents100 retryclicks onfailedenvironmentOOMYou'vegotRA'dNightphonecallSAWdoesn'tworkActualbugsev 2, butno one onthe bridgesev0No input= nooutputNo oneknows howmetric isemitted"Why Isee logs,but notmetrics?"SDPbypassReleaserollbackCustomer-facingRCASCDAzSysLockAlbussev1sev2Probablyit's anetworkingglitchMisroutedincidentNoresponseafter 7daysNoFlyZone20 newincidents100 retryclicks onfailedenvironmentOOMYou'vegotRA'dNightphonecallSAWdoesn'tworkActualbug

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