Repository navigation
Track server content requests separately in Scarf - #1398
Merged
Merged
Conversation
|
|
Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configuration
📒 Files selected for processing: 4
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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
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.
Changes
Track successful HTML and Markdown content requests at the Cloudflare Worker entry, including crawlers that never execute JavaScript. Forward the visitor IP and user agent to Scarf and include Cloudflare bot classification when available.
Server traffic uses a separate
server_requestevent. Browser page views and pixels are unchanged; these overlapping datasets must not be summed as unique visitors. Delivery runs in the background with a timeout, respects DNT/GPC, and excludes private routes, assets, redirects, and failed responses.Validation
Six focused tracking tests pass. Full type, lint, unit, chat, and desktop checks passed again after rebasing onto current main. The integration preserves the docs header/timing wrapper and staging analytics exclusion.