Traffic Monitor marks topology-based delivery services as unavailable

[zrhoffman]

I'm submitting a ...

• bug report
• new feature / enhancement request
• improvement request (usability, performance, tech debt, etc.)
• other

Traffic Control components affected ...

• CDN in a Box
• Documentation
• Grove
• Traffic Control Client
• Traffic Monitor
• Traffic Ops
• Traffic Ops ORT
• Traffic Portal
• Traffic Router
• Traffic Stats
• Traffic Vault
• unknown

Current behavior:

Traffic Monitor marks topology-based delivery services as unavailable. From the logs:

cache.go:375: 2020-07-24T14:23:49.450102741Z: CRConfig does not have delivery service demo1, but traffic monitor poller does; skipping

trafficmonitor_1            | INFO: stat.go:54: 2020-07-24T14:20:08.753631349Z: CreateStats not adding availability data for 'edge': not found in DeliveryServices
trafficmonitor_1            | INFO: stat.go:54: 2020-07-24T14:20:08.753641187Z: CreateStats not adding availability data for 'mid': not found in DeliveryServices
trafficmonitor_1            | INFO: stat.go:136: 2020-07-24T14:20:08.753646906Z: CreateStats not adding disabledLocations for 'demo1': not found in Stats

Expected / new behavior:

Topology-based delivery services should have the potential to be marked as available. Expected output:

trafficmonitor_1            | 1595954995.290 host="demo1", type=Delivery Service, available=true, msg="available caches"
trafficmonitor_1            | 1595954995.290 host="demo1", type=DELIVERYSERVICE, available=true, msg="REPORTED - available"

Minimal reproduction of the problem with instructions:

1. Make topology-based delivery service
2. Perform CDN snapshot
3. Look at Traffic Monitor logs