The CRConfig only has what Traffic Router needs. The `monitoring.json` has things in it that Traffic Monitor needs, that Traffic Router doesn't. Specifically Server Profile data, specifically thresholds and poll times.
The `monitoring.json` does also have a ton of data that's also in the CRConfig. We should really clean that up. The Monitor treats CRConfig as authoritative, and ignores any data in monitoring.json that's also in CRConfig. But it's not really hurting anything. I wouldn't be opposed to combining them, and just having one object, and then the Router would just ignore the data it didn't need. It'd certainly make synchronization easier; there are some seriously nasty races between them; see https://github.com/apache/trafficcontrol/issues/1739 and https://github.com/apache/trafficcontrol/issues/1738. But it'd also mean wasting bandwidth and potentially CPU on the Router. On Mon, Dec 30, 2019 at 11:20 AM Eric Friedrich <[email protected]> wrote: > What is the difference between monitoring.json and CRConfig? Traffic > Monitor fetches both of them and the CRConfig seems like a superset of > monitoring. > > > --Eric >
