add snapstart span #911
Merged
add snapstart span #911
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
jchrostek-dd
force-pushed
the
john/snapstart-span
branch
from
318ae3f to
9ea2a19
Compare
| pub duration_ms: f64, | ||
| } | ||
|
|
||
| /// Restore report metrics |
Contributor
There was a problem hiding this comment.
Please add test coverage for new struct and new field above.
Contributor
|
besides the unit tests, can we consider adding tests in bottlecap/tests/ to verify: |
| { | ||
| error!("Failed to send platform restore report to processor: {}", e); | ||
| } | ||
| } |
Contributor
There was a problem hiding this comment.
Can we log error in case metrics is None as it may indicate malformed data?
Contributor
litianningdatadog
left a comment
litianningdatadog
left a comment
There was a problem hiding this comment.
Left some comments.
litianningdatadog
approved these changes
Nov 6, 2025
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.
Task
https://datadoghq.atlassian.net/browse/SVLS-7836?atlOrigin=eyJpIjoiMWNmZTMzOGE4NGEwNDE4MTk5Njk0N2ZmMmU3MzExMjgiLCJwIjoiaiJ9
Overview
The extension neither creates SnapStart spans nor emits SnapStart metrics. This PR adds both.
When a lambda with snapshot enabled is invoked for the first time, we get
Platform.RestoreStartandPlatform.RestoreReport. These effectively take the place ofPlatform.InitStartandPlatform.InitReportevents, so our code flow is pretty much identical to how we handle the cold start span and duration metric.Note - When a SnapStart instance is restored, we actually receive the
Platform.InitStartandPlatform.InitReportevents in addition to thePlatform.RestoreStartandPlatform.RestoreReport. However, theInitevents are not from the sandbox starting for that invoke. TheseInitevents are actually generated from when the Snapshot is created. This is very misleading - You can see that this trace is more than 3 hours long. The lambda was invoked more than 3 hours after the snapshot version was created. (This is the current experience).Testing
I deployed my own extension with the changes and confirmed we are now getting a restore span and not an init span, link.