Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Log stats after every request?

Open
#264 0 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
ruby
Domain
observability

Research direction

Start by tracing the request lifecycle around the proposed after_action hook and the cache operations mentioned in the issue. Determine which hit, miss, write, latency, and memoization data IdentityCache exposes, then verify that the resulting statistics can be emitted to $stdout for transport to Librato.

Written by the indexing model from the issue text.

Description

I would like to send # of cache hits, # cache misses, # cache writes, cache store latency, memoized cache hits, etc to $stdout (for transport to Librato). Is any of this information available for me to stick in an after_action or something?

Dominant language
Ruby
Stars
2k
Forks
175
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Shopify/identity_cache

All issues in Shopify/identity_cache

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.