"Why Isee logs,but notmetrics?"sev1No oneknows howmetric isemittedYou'vegotRA'dsev2SAWdoesn'twork20 newincidentsReleaserollbackOOMNoresponseafter 7daysAzSysLockMisroutedincidentsev0NoFlyZoneAlbus100 retryclicks onfailedenvironmentSDPbypassActualbugSCDNightphonecallNo input= nooutputsev 2, butno one onthe bridgeProbablyit's anetworkingglitchCustomer-facingRCA"Why Isee logs,but notmetrics?"sev1No oneknows howmetric isemittedYou'vegotRA'dsev2SAWdoesn'twork20 newincidentsReleaserollbackOOMNoresponseafter 7daysAzSysLockMisroutedincidentsev0NoFlyZoneAlbus100 retryclicks onfailedenvironmentSDPbypassActualbugSCDNightphonecallNo input= nooutputsev 2, butno one onthe bridgeProbablyit's anetworkingglitchCustomer-facingRCA

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