"Why Isee logs,but notmetrics?"You'vegotRA'dsev 2, butno one onthe bridgeNo input= nooutputOOM100 retryclicks onfailedenvironmentNightphonecallNoresponseafter 7daysProbablyit's anetworkingglitchsev2Customer-facingRCANoFlyZonesev1SCDSAWdoesn'tworkAlbusReleaserollbackAzSysLockSDPbypassMisroutedincidentActualbugsev020 newincidentsNo oneknows howmetric isemitted"Why Isee logs,but notmetrics?"You'vegotRA'dsev 2, butno one onthe bridgeNo input= nooutputOOM100 retryclicks onfailedenvironmentNightphonecallNoresponseafter 7daysProbablyit's anetworkingglitchsev2Customer-facingRCANoFlyZonesev1SCDSAWdoesn'tworkAlbusReleaserollbackAzSysLockSDPbypassMisroutedincidentActualbugsev020 newincidentsNo oneknows howmetric isemitted

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