The Redis GitHub GET-response cache (src/selfhost/redis-response-cache.ts) emits zero Prometheus metrics, unlike the in-isolate GitHub HTTP cache which records hit/miss/set/coalesced via recordGitHubCacheMetric (src/github/client.ts:127). Operators have no way to see whether GITHUB_CACHE_TTL_SECONDS is actually saving REST budget. Add a gittensory_redis_gh_response_cache_total{result} counter (hit on get()-returns-value, miss on get()-returns-null, set on set()) incremented inside createRedisResponseCache.
Deliverables
References
src/selfhost/redis-response-cache.ts:21
src/selfhost/redis-response-cache.ts:43
src/github/client.ts:127
src/selfhost/metrics.ts:48
size: S · gittensor:feature
The Redis GitHub GET-response cache (src/selfhost/redis-response-cache.ts) emits zero Prometheus metrics, unlike the in-isolate GitHub HTTP cache which records hit/miss/set/coalesced via recordGitHubCacheMetric (src/github/client.ts:127). Operators have no way to see whether GITHUB_CACHE_TTL_SECONDS is actually saving REST budget. Add a gittensory_redis_gh_response_cache_total{result} counter (hit on get()-returns-value, miss on get()-returns-null, set on set()) incremented inside createRedisResponseCache.
Deliverables
References
src/selfhost/redis-response-cache.ts:21src/selfhost/redis-response-cache.ts:43src/github/client.ts:127src/selfhost/metrics.ts:48size: S · gittensor:feature