[TT-16529] Add cache_hit field to Gateway access logs #7717
+112
−2
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.
Summary
Adds a new
cache_hitfield to the Tyk Gateway access logs that indicates whether a response was served from the cache.CacheHitcontext key for passing cache status through request contextcache_hit=truein Redis cache middleware when serving cached responsescache_hitfield in all access log entries (defaults tofalsefor non-cached responses)Test plan
go test ./internal/httputil/accesslog/...)go build ./ctx/... ./gateway/... ./internal/httputil/accesslog/...)go vet ./gateway/...)cache_hit=truewhen response is served from cachecache_hit=falsewhen response is from upstreamRelated Issues
🤖 Generated with Claude Code