-
Notifications
You must be signed in to change notification settings - Fork 778
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add telemetry to auto provisioning #7984
Conversation
🦋 Changeset detectedLatest commit: ef8d644 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
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 |
A wrangler prerelease is available for testing. You can install this latest build in your project with: npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13078166767/npm-package-wrangler-7984 You can reference the automatically updated head of this PR with: npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/prs/7984/npm-package-wrangler-7984 Or you can use npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13078166767/npm-package-wrangler-7984 dev path/to/script.js Additional artifacts:cloudflare-workers-bindings-extension: wget https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13078166767/npm-package-cloudflare-workers-bindings-extension-7984 -O ./cloudflare-workers-bindings-extension.0.0.0-v4f573b88f.vsix && code --install-extension ./cloudflare-workers-bindings-extension.0.0.0-v4f573b88f.vsix create-cloudflare: npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13078166767/npm-package-create-cloudflare-7984 --no-auto-update @cloudflare/kv-asset-handler: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13078166767/npm-package-cloudflare-kv-asset-handler-7984 miniflare: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13078166767/npm-package-miniflare-7984 @cloudflare/pages-shared: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13078166767/npm-package-cloudflare-pages-shared-7984 @cloudflare/unenv-preset: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13078166767/npm-package-cloudflare-unenv-preset-7984 @cloudflare/vite-plugin: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13078166767/npm-package-cloudflare-vite-plugin-7984 @cloudflare/vitest-pool-workers: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13078166767/npm-package-cloudflare-vitest-pool-workers-7984 @cloudflare/workers-editor-shared: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13078166767/npm-package-cloudflare-workers-editor-shared-7984 @cloudflare/workers-shared: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13078166767/npm-package-cloudflare-workers-shared-7984 @cloudflare/workflows-shared: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13078166767/npm-package-cloudflare-workflows-shared-7984 Note that these links will no longer work once the GitHub Actions artifact expires.
Please ensure constraints are pinned, and |
ae3f409
to
16517ea
Compare
public accountId: string | ||
public accountId: string, | ||
/** For telemetry */ | ||
public summary: Record<string, number> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
An instance of this class represents a single binding—it feels odd to be passing in a record of multiple bindings here? Why does this need to be done insdie the class? Can't we just count the number of items in pendingResources?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah it is odd :/ i wanted access to the inherit/create/connect methods to record what happens to each resource, not just that they get provisioned in some way (connected or created), especially as some resources get connected before runProvisioningFlow
and some after.
Although now that i'm revisiting it, i think that's probably a level of granularity that isn't necessary/important and we can just count pendingResources... yeah i'll simplify this
"wrangler": patch | ||
--- | ||
|
||
feat: add telemetry to experimental auto-provisioning |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a sanity check: This is a patch because it is an experimental feature, right?
@@ -30,6 +31,7 @@ describe("--x-provision", () => { | |||
const { setIsTTY } = useMockIsTTY(); | |||
|
|||
beforeEach(() => { | |||
logger.loggerLevel = "debug"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You might need to restore the loggerLevel after the test or it will create a side effect for the rest of the tests.
Fixes [DEVX-1618]
Sends a new adhoc telemetry event since the dispatcher cannot (currently) be used in command handlers.
draft amplitude dash: https://app.amplitude.com/analytics/cloudflare/dashboard/4h1lunzd