[Instrumentation.AWSLambda] Incoming FaaS Span attributes: detect and set attribute for cold start #2032
Labels
comp:instrumentation.awslambda
Things related to OpenTelemetry.Instrumentation.AWSLambda
enhancement
New feature or request
Comments
github-actions
bot
added
the
comp:instrumentation.awslambda
rypdal
added a commit
to rypdal/opentelemetry-dotnet-contrib
that referenced
this issue
Sep 3, 2024
rypdal
added a commit
to rypdal/opentelemetry-dotnet-contrib
that referenced
this issue
Sep 4, 2024
rypdal
added a commit
to rypdal/opentelemetry-dotnet-contrib
that referenced
this issue
Sep 4, 2024
rypdal
added a commit
to rypdal/opentelemetry-dotnet-contrib
that referenced
this issue
Sep 4, 2024
Co-authored-by: Christian Neumüller <christian+github@neumueller.me>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Component
OpenTelemetry.Instrumentation.AWSLambda
Is your feature request related to a problem?
AWS Lambda instrumentation sets required incoming FaaS Span attribute
faas.trigger. It would be useful also to set recommendedfaas.coldstart. See https://github.com/open-telemetry/semantic-conventions/blob/main/docs/faas/faas-spans.md#incoming-faas-span-attributesWhat is the expected behavior?
Cold start is detected and the attribute
faas.coldstartis set.Which alternative solutions or features have you considered?
Not required.
Additional context
No response
The text was updated successfully, but these errors were encountered: