Releaserollbacksev0sev1"Why Isee logs,but notmetrics?"OOMsev 2, butno one onthe bridgeSCD100 retryclicks onfailedenvironmentSDPbypassCustomer-facingRCAAlbusNightphonecallsev2NoFlyZoneNoresponseafter 7daysProbablyit's anetworkingglitch20 newincidentsNo oneknows howmetric isemittedNo input= nooutputMisroutedincidentSAWdoesn'tworkActualbugYou'vegotRA'dAzSysLockReleaserollbacksev0sev1"Why Isee logs,but notmetrics?"OOMsev 2, butno one onthe bridgeSCD100 retryclicks onfailedenvironmentSDPbypassCustomer-facingRCAAlbusNightphonecallsev2NoFlyZoneNoresponseafter 7daysProbablyit's anetworkingglitch20 newincidentsNo oneknows howmetric isemittedNo input= nooutputMisroutedincidentSAWdoesn'tworkActualbugYou'vegotRA'dAzSysLock

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