Problem
cacheHitRatio counts only rows where x_edge_result_type is Hit, RefreshHit or Miss, and its own description states that a response generated by a CloudFront Function is one of the things that excludes. Nobody has checked. The CloudFront documentation enumerates no x-edge-result-type value for a function-generated response, and AGENTS.md has carried this as an open measurement since #99. If the real value turns out to be Hit, every beacon event counts as a cache hit, and the ratio climbs with beacon traffic rather than with caching.
Current behaviour
status-codes excludes beacon rows by path, through outsideTheBeaconPath in src/beacon-rows.ts, which #107 added. cache-hit-ratio excludes nothing by path and relies entirely on the value in that column. Simulated CloudFront cannot settle this, because the value is whatever the real service writes.
Desired behaviour
The value is read off a real delivery, written down in docs/beacon-path/, and the rollups are correct given whatever it turns out to be.
Acceptance criteria
Blocked on
A site deploying BeaconPath. That is possible from v0.2.0 onward, which is the first release carrying the construct.
Problem
cacheHitRatiocounts only rows wherex_edge_result_typeisHit,RefreshHitorMiss, and its own description states that a response generated by a CloudFront Function is one of the things that excludes. Nobody has checked. The CloudFront documentation enumerates nox-edge-result-typevalue for a function-generated response, and AGENTS.md has carried this as an open measurement since #99. If the real value turns out to beHit, every beacon event counts as a cache hit, and the ratio climbs with beacon traffic rather than with caching.Current behaviour
status-codesexcludes beacon rows by path, throughoutsideTheBeaconPathinsrc/beacon-rows.ts, which #107 added.cache-hit-ratioexcludes nothing by path and relies entirely on the value in that column. Simulated CloudFront cannot settle this, because the value is whatever the real service writes.Desired behaviour
The value is read off a real delivery, written down in
docs/beacon-path/, and the rollups are correct given whatever it turns out to be.Acceptance criteria
BeaconPathhas served beacon events and delivered the logs.x-edge-result-typevalue those rows carry is recorded indocs/beacon-path/.cache-hit-ratiois checked against that value, and gains a beacon-row filter if it needs one.Blocked on
A site deploying
BeaconPath. That is possible from v0.2.0 onward, which is the first release carrying the construct.