-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Send OpenTelemetry traces to the datadog via the extension #100
Comments
Cross referencing issue in repo that contains the actual code |
Hi Matthias. Thanks for the issue, sorry for the delay in writing this response. Like it was identified in the other thread, we have stripped OTel support from the Serverless build. Unfortunately, it's a bit more complicated than reversing the build tags, we have to rearrange some internals to correctly serve the OTel API. We are currently planning work for supporting OTel directly in the extension. We'll post an update on this ticket when we have more info. |
Also interested |
cc: @purple4reina |
I'm pleased to announce that we have released v41 of the Datadog AWS Lambda Extension with OpenTelemetry support. You can enable the feature by setting either |
Is there any more to this other than setting the environment variable? I can see trace relating to the Lambda, but the traces generated by my service don't seem to be getting received (or forwarded?) by the agent. |
🐸 Hey everyone, I'm going to close this ticket since this seems to have been fixed a while ago. Here are some docs around it. If there is any concern, or you are stuck instrumenting your resources with OTel and the Datadog Extension. Feel free to create a ticket on our support page! Feel free to re-open if there's any issues or concerns. |
I would like to instrument my Lambda function using OpenTelementry. I know ADOT (AWS Distro for OpenTelementry) exists but it seems that I would have to sacrifice some features (appsec, enhanced metrics, log & trace correlation, etc) if I only used that. If I used both ADOT and the Datadog extension then I'd have to include more Lambda Layers.
I would like to activate the OTLP ingestion. I tried setting the
DD_OTLP_CONFIG_RECEIVER_PROTOCOLS_HTTP_ENDPOINT=localhost:4318
environment variable but when I check the port is not in use. Is it possible to run the OTLP ingestion in lambda?The text was updated successfully, but these errors were encountered: