[workers-shared] Split customer-facing asset analytics#14711
Draft
ericclemmons wants to merge 2 commits into
Draft
[workers-shared] Split customer-facing asset analytics#14711ericclemmons wants to merge 2 commits into
ericclemmons wants to merge 2 commits into
Conversation
🦋 Changeset detectedLatest commit: b92557c The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Contributor
|
UnknownError: ProviderInitError |
Contributor
|
@ericclemmons Bonk workflow failed. Check the logs for details. View workflow run · To retry, trigger Bonk again. |
Contributor
|
✅ All changesets look good |
@cloudflare/autoconfig
@cloudflare/config
create-cloudflare
@cloudflare/deploy-helpers
@cloudflare/kv-asset-handler
miniflare
@cloudflare/pages-shared
@cloudflare/unenv-preset
@cloudflare/vite-plugin
@cloudflare/vitest-pool-workers
@cloudflare/workers-auth
@cloudflare/workers-editor-shared
@cloudflare/workers-utils
wrangler
commit: |
Contributor
|
UnknownError: ProviderInitError |
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.
tl;dr – Write customer-safe Asset Worker request metrics to a dedicated Ready Analytics binding.
Asset Worker currently mixes operational service telemetry with fields consumed by the customer-facing Workers Analytics GraphQL API. This introduces a separate
CUSTOMER_ANALYTICSwrite path with an explicit allowlist: account/script identity, colo, status, hostname, cache status, and the customer Worker version UUID.The existing
ANALYTICSpayload and its platform-owned Asset Worker buildversionremain unchanged. Customer events are emitted once from the inner request handler so the new dataset does not expose operational fields or double-count outer and inner entrypoints.This producer is one part of the rollout. Ready Analytics must provision and map the dedicated customer namespace, and Workers Pipelines must populate
assetConfig.script_version_id, before GraphQL and Stratus consume it.References: Google Chat design thread · Ready Analytics !1388 · GraphQL !3466 · Stratus !40670