Actualbugsev 2, butno one onthe bridgeSCDAlbusOOMCustomer-facingRCANoFlyZonesev2100 retryclicks onfailedenvironmentMisroutedincident20 newincidentsNo oneknows howmetric isemitted"Why Isee logs,but notmetrics?"Noresponseafter 7daysYou'vegotRA'dNightphonecallSAWdoesn'tworkSDPbypasssev1AzSysLockProbablyit's anetworkingglitchsev0No input= nooutputReleaserollbackActualbugsev 2, butno one onthe bridgeSCDAlbusOOMCustomer-facingRCANoFlyZonesev2100 retryclicks onfailedenvironmentMisroutedincident20 newincidentsNo oneknows howmetric isemitted"Why Isee logs,but notmetrics?"Noresponseafter 7daysYou'vegotRA'dNightphonecallSAWdoesn'tworkSDPbypasssev1AzSysLockProbablyit's anetworkingglitchsev0No input= nooutputReleaserollback

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