"Why Isee logs,but notmetrics?"Noresponseafter 7dayssev 2, butno one onthe bridgesev2sev0100 retryclicks onfailedenvironmentYou'vegotRA'd20 newincidentssev1Customer-facingRCAProbablyit's anetworkingglitchOOMSDPbypassNightphonecallNo oneknows howmetric isemittedSAWdoesn'tworkActualbugMisroutedincidentNo input= nooutputReleaserollbackAlbusNoFlyZoneSCDAzSysLock"Why Isee logs,but notmetrics?"Noresponseafter 7dayssev 2, butno one onthe bridgesev2sev0100 retryclicks onfailedenvironmentYou'vegotRA'd20 newincidentssev1Customer-facingRCAProbablyit's anetworkingglitchOOMSDPbypassNightphonecallNo oneknows howmetric isemittedSAWdoesn'tworkActualbugMisroutedincidentNo input= nooutputReleaserollbackAlbusNoFlyZoneSCDAzSysLock

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