rawlinp opened a new issue #6663: URL: https://github.com/apache/trafficcontrol/issues/6663
<!-- ************ STOP!! ************ If this issue identifies a security vulnerability, DO NOT submit it! Instead, contact the Apache Traffic Control Security Team at [email protected] and follow the guidelines at https://apache.org/security regarding vulnerability disclosure. - For *SUPPORT QUESTIONS*, use the #traffic-control channel on the ASF slack (https://s.apache.org/tc-slack-request) or the Traffic Control Users mailing list (send an email to [email protected] to subscribe). - Before submitting, please **SEARCH GITHUB** for a similar issue or PR * https://github.com/apache/trafficcontrol/issues * https://github.com/apache/trafficcontrol/pulls --> <!-- Do not submit security vulnerabilities or support requests here - see above --> ## This Improvement request (usability, performance, tech debt, etc.) affects these Traffic Control components: <!-- delete all those that don't apply --> - Traffic Ops - Traffic Router ## Current behavior: <!-- Describe how the current features are insufficient. --> The CRConfig snapshot contains `MID` caches because Traffic Monitor uses data from the CRConfig currently. ## New behavior: <!-- Describe how this change would improve Traffic Control --> Once https://github.com/apache/trafficcontrol/issues/6627 is completed, we should be able to exclude `MID` caches from the CRConfig, because Traffic Router does not care about `MID` caches at all. It only needs to know about `EDGE` caches. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
