# this is really dense...
# I think I'm trying to show are Issues:
# 1. source: where is the problem (LAN, ISP, DNS, laptop, VPN, etc...)
# 2. cause: the (probable) cause of the problem (eg: wifi congestion??)every Issue should have that diagnosis bit
# 3. name: the name of the problem detected (swapped)
# and the Issue history/status
# 4. number of times the issue occurred
# 5. when it last happened
  ⚠ LAN: high latency to gateway — wifi congestion or bad link (68 ms) (10x, ongoing)
  ⚠ LAN: high jitter to gateway — unstable wifi/LAN (62 ms) (8x, ongoing)
    ISP/internet: moderate latency beyond gateway (81 ms above LAN) (3x, 1m ago)
    ISP/internet: high jitter — unstable connection (63 ms beyond LAN) (1x, 1m ago)

# We can highlight the bad values
# if we are smart (eg: high rtt, high loss, high jitter)
#
# we can keep the table-ish formatting for now but I don't want to assume
# it will stay. We need to highlight sections that are having problems
# there may be a missing piece of the data model to capture this because
# I don't think probe result can know if the jitter is too high
  LAN:           68.1 ms rtt, 0% loss, 61.7 ms jitter (gateway 192.168.66.1)
  ISP/internet: 112.4 ms rtt, 0% loss, 65.4 ms jitter
