Open
Conversation
Contributor
Contributor
|
the PR description says:
is it actually opt-in? the console did not ask me anything yet it's sending events. |
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.

Adds anonymous, opt-in usage telemetry to the web console. Events are stored locally in IndexedDB and flushed to the server in batches.
Telemetry infrastructure (ConsoleEventTracker module)
trackEvent(name, payload?): fire-and-forget entry point; writes to IndexedDB via Dexie (db.ts)sendPipeline.ts: background flush loop that runs every 5 s when there are pending eventsconsole-events-configto get the server-side cursor (lastUpdated), then POSTs only newer events viaadd-console-eventsMAX_BATCH_SIZE= 1 000 events per POST; successfully sent entries are deleted from IndexedDB immediatelytrimToMaxRows(10 000)evicts the oldest events to bound local storage