Record fetching backend per URL in run reports#306
Merged
Conversation
Add a "backend" field to each entry in reports/<run_id>.json: the fetcher recorded on the stored capture (set for stored/deduped/ cache_hit outcomes, "" when nothing was fetched, e.g. errors). This lets downstream tooling attribute per-domain cost by backend without changing the cost estimation itself. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Each run-report row now records which backend fetched the URL (
backend, empty when nothing was fetched). This makes it possible to see which sites need paid backends and attribute cost per domain. Note: on cache hits the backend comes from the original capture, so cost analysis should only countstored/dedupedrows.