Noresponseafter 7dayssev1Probablyit's anetworkingglitchSCD100 retryclicks onfailedenvironmentNo oneknows howmetric isemitted"Why Isee logs,but notmetrics?"OOMAlbussev220 newincidentsNo input= nooutputCustomer-facingRCANoFlyZoneSDPbypassActualbugMisroutedincidentsev 2, butno one onthe bridgeAzSysLockSAWdoesn'tworkNightphonecallYou'vegotRA'dsev0ReleaserollbackNoresponseafter 7dayssev1Probablyit's anetworkingglitchSCD100 retryclicks onfailedenvironmentNo oneknows howmetric isemitted"Why Isee logs,but notmetrics?"OOMAlbussev220 newincidentsNo input= nooutputCustomer-facingRCANoFlyZoneSDPbypassActualbugMisroutedincidentsev 2, butno one onthe bridgeAzSysLockSAWdoesn'tworkNightphonecallYou'vegotRA'dsev0Releaserollback

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