chore(renderer): temporary egress-arm diagnostics#314
Merged
Conversation
Log the chrome_proxy auto-egress arm construction inputs and gate conditions (warn/egress_diag) to trace why the residential recovery arm never fires on prod for a datacenter-IP hard block. Reverted after the one deploy that captures the failing condition.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Temporary warn logs to trace why the chrome_proxy residential recovery arm never fires on prod for a datacenter-IP hard block (Wikipedia). Reverted after the capture deploy.