Skip to content
This repository was archived by the owner on May 7, 2026. It is now read-only.

Log retrieve route request params to Redis for analytics - #19

Merged
zarathustra323 merged 2 commits into
mainfrom
log-requests
May 5, 2026
Merged

Log retrieve route request params to Redis for analytics#19
zarathustra323 merged 2 commits into
mainfrom
log-requests

Conversation

@zarathustra323

@zarathustra323 zarathustra323 commented May 5, 2026

Copy link
Copy Markdown
Member

Increments a Redis counter on every request to the /retrieve route using the key most_popular_content:request-log:{tenant}:{realm}:{granularity}:{limit}. This provides visibility into which tenant/realm/granularity combinations are being queried and what limits callers are actually requesting. The latter will inform a future change to how content popularity data is stored — rather than storing all content, we can cap storage at the highest limit we observe in practice.

Also included: bumps actions/checkout, actions/setup-node, and actions/cache from v1/v2 to v4 in the Node.js CI workflow to resolve a GitHub Actions deprecation error that was causing builds to fail.

@zarathustra323

Copy link
Copy Markdown
Member Author

@zarathustra323
zarathustra323 merged commit 85c60c2 into main May 5, 2026
4 checks passed
@zarathustra323
zarathustra323 deleted the log-requests branch May 5, 2026 18:19
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant