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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gh 1763/metrics feature/new triggers for broken page pings #418
Gh 1763/metrics feature/new triggers for broken page pings #418
Changes from 1 commit
4ecd3d09c740831ed578e99305fc52e9a7a311b498dd1d21549281a85e5d996f2c49ab0664aa528da0dfe7cd1bce0076c1b9cf1ee81aa786File filter
Jump to
Add local tracker unblock trigger for Metrics broken page watcher.
christophertinoJul 23, 2019
Member
@wlycdgr seems like this would be triggered when adding to and removing from the whitelist. Do we need both cases? If not we should check against
sitePolicyto look for just the addition portion.wlycdgrJul 23, 2019
•
edited
Author
Member
@christophertino Updated. Since
sitePolicyis not currently being sent to the background and would have had to be added anyway, I instead send abrokenPageMetricsWhitelistSitebool to express intent more clealry and test for it inPanelData#set