jpappa200 opened a new issue, #7674: URL: https://github.com/apache/trafficcontrol/issues/7674
<!-- ************ 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 Feature Request affects these Traffic Control components: <!-- delete all those that don't apply --> - Traffic Control Cache Config (`t3c`, formerly ORT) - Traffic Ops - Traffic Portal ## Description <!-- Describe how the current ATC features are insufficient and how this new feature would improve Traffic Control --> Right now in TC we have a checkmark to indicate caches are up to date and/or update has succeeded. We have a clock to signal a cache has a pending update. I would like to add an `X` flag to indicate an update failure. We really don't have any way to indicate a failure unless we're watching the t3c logs. A lot of times t3c will clear the update flag on failure otherwise every 3 min (or what ever update interval is set) t3c will pull the configs and do a full run and fail repeatedly until the issue is fixed. On failure I would like t3c to set the update failed flag `X` in TO as an indication a failure has occurred and should be investigated. Also t3c will not consider the `X` as a pending update, and once the server is fixed updates could be queued again to signal an update is pending. -- 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]
