chore: Track pipeline count and node distribution at session start#2163
Merged
morgan-wowk merged 1 commit intomasterfrom Apr 30, 2026
Merged
chore: Track pipeline count and node distribution at session start#2163morgan-wowk merged 1 commit intomasterfrom
morgan-wowk merged 1 commit intomasterfrom
Conversation
🎩 PreviewA preview build has been created at: |
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
morgan-wowk
force-pushed
the
pipeline-analytics
branch
3 times, most recently
from
6477b92 to
143e989
Compare
morgan-wowk
force-pushed
the
pipeline-analytics
branch
from
143e989 to
10ed9c9
Compare
maxy-shpfy
reviewed
Apr 24, 2026
morgan-wowk
force-pushed
the
pipeline-analytics
branch
from
10ed9c9 to
2fb1bdc
Compare
maxy-shpfy
reviewed
Apr 24, 2026
Comment on lines
+82
to
+87
| "11_to_20": 0, | ||
| "21_to_49": 0, | ||
| "50_plus": 0, | ||
| }; | ||
|
|
||
| try { |
Collaborator
There was a problem hiding this comment.
I would change buckets instead of +10 increment, use fibonacci or progressive/exp scale, so we can have visibility into 200+ nodes
Author
There was a problem hiding this comment.
CC: @camielvs Sound good to you? These buckets were your suggestion
Collaborator
There was a problem hiding this comment.
sure. I just pulled these off the top of my head. Happy to go with something more granular, e.g. fibonacci. Though highly irregular bucket width could make comparisons tricky
Author
There was a problem hiding this comment.
We moved to use fibonacci buckets.
morgan-wowk
force-pushed
the
pipeline-analytics
branch
from
2fb1bdc to
c1a0f95
Compare
camielvs
approved these changes
Apr 24, 2026
Author
Merge activity
|
morgan-wowk
force-pushed
the
pipeline-analytics
branch
from
c1a0f95 to
19685dd
Compare
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
3 participants
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.
Impact on existing application
This tracking runs asynchronously, only once per session without interrupting the render.
Screenshots (if applicable)
Description
Adds a
useSessionPipelineStatshook that fires asession.pipeline_stats.startanalytics event once per browser-tab session. The event includes the total number of pipelines and a bucketed distribution of node counts (0,1_to_5,6_to_20,21_plus) across all pipelines found in both the current Dexie-based storage and the legacy localForage storage.Node counting recursively flattens inline subgraphs, replacing each subgraph task with its own constituent nodes. A
sessionStorageguard prevents duplicate fires within the same tab session.The hook is mounted via a
SessionPipelineStatsTrackercomponent placed insidePipelineStorageProviderinRootLayout.Related Issue and Pull requests
Type of Change
Checklist
Test Instructions
session.pipeline_stats.startevent is present withtotal_pipelinesandpipeline_node_bucketsproperties.Additional Comments
Folders that require permission are skipped during enumeration. Pipelines that fail to parse are still counted toward
total_pipelinesto avoid undercounting. If the legacy store is unavailable, the Dexie-based count is still reported.