Restores logging the cache status. #6667
Merged
Conversation
This file contains 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
ocket8888
added
new feature
|
@ocket8888 I'm unable to see any logs for the failing tests. I can't imagine why the Weasel license checks failed. CI issue? Could you restart the CI tests? |
|
The license tests failed because
I haven't looked at the other yet, but I'm sure it's the same. |
When the tc-health-client was switched to using the combined TM CrStates endpoint, the ability to log the cache status was lost, Issue apache#6448. PR apache#6612 adds the cache status field to the TM CrStates endpoint allowing cache status to be logged again. This PR adds back the cache status logging.
jrushford
force-pushed
the
crstates-with-status-field
branch
from
3ebb240
to
961f0c1
Compare
rawlinp
approved these changes
Mar 30, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When the tc-health-client was switched to using the combined
TM CrStates endpoint, the ability to log the cache status was
lost, Issue #6448. PR #6612 adds the cache status field to the
TM CrStates endpoint allowing cache status to be logged again.
This PR adds back the cache status logging.
Which Traffic Control components are affected by this PR?
What is the best way to verify this PR?