AzSysLockMisroutedincidentActualbug20 newincidentssev 2, butno one onthe bridgeNoFlyZonesev2ReleaserollbackSCDOOMProbablyit's anetworkingglitchCustomer-facingRCASAWdoesn'tworkSDPbypassNo input= nooutputsev0100 retryclicks onfailedenvironmentNo oneknows howmetric isemittedNoresponseafter 7daysYou'vegotRA'dNightphonecallsev1"Why Isee logs,but notmetrics?"AlbusAzSysLockMisroutedincidentActualbug20 newincidentssev 2, butno one onthe bridgeNoFlyZonesev2ReleaserollbackSCDOOMProbablyit's anetworkingglitchCustomer-facingRCASAWdoesn'tworkSDPbypassNo input= nooutputsev0100 retryclicks onfailedenvironmentNo oneknows howmetric isemittedNoresponseafter 7daysYou'vegotRA'dNightphonecallsev1"Why Isee logs,but notmetrics?"Albus

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