feat: add tarball bundling timing metric for Edge Functions and expose it via manifest/schema #6786
Conversation
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
…e it via manifest/schema
eduardoboucas
approved these changes
Nov 21, 2025
JakeChampion
changed the title
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.
Summary
We want to track how long the tarball flow takes to complete as part of https://linear.app/netlify/issue/RUN-1989/ensure-were-tracking-the-right-metrics-on-the-shared-dashboard#comment-d606d379
I've added a new metric type which our underlying statsd client (hot-shots) supports, timing - we then add a new field to the manifest to put the timing into, so that our existing edge-functions core plugin can pull it out and hand it to the statsd client.