Traffic Monitor `monitoring.json` Is Not Synchronized with CRConfig

[rob05c]

The Monitor gets data from 2 TO endpoints, monitoring.json and the CRConfig; the monitoring.json is live data, not a snapshot.

So, for example, if you remove the health.polling.url from a Profile, or delete the Profile, or rename the Profile, in preparation to snapshot a version/name change, it disappears from monitoring.json, and the Monitor doesn’t know where to poll anymore. Until it gets the updated Snapshot.

The monitoring.json data needs Snapshotted in sync with the CRConfig (either put in the CRConfig itself, or the same 'snapshot' button creates a synchronized monitoring.json Snapshot).

This will allow users to make large, lengthy changes, and Snapshot atomically, without breaking Monitor polling in unexpected ways in the meantime.

Note the monitoring.json data overlaps with the CRConfig a great deal. The monitor necessarily uses the CRConfig Snapshot for all overlapping data. Hence, if the data is combined it really isn't that much to add to the CRConfig, and if it isn't combined, the overlapping data should be removed as it isn't used.

[rob05c]

I'm assigning myself, but I likely won't have time soon, if anyone else wants to fix this, feel free to take it from me.

[rob05c]

This is related to but distinct from #1739 . Symptoms will often be the result of some combination of both bugs.