Comments (2)
Hi @taylorsmithgg , thanks for raising this issue!
Actually, this links to the "Getting Started - Lambda Support for .NET" docs intentionally because .NET is an example of a language that has no layer which can't automatically instrument the OTel SDK like some other layers do 😕 So as a "Collector Layer", it only provides the ADOT Collector which can be used by .NET Lambdas in the absence of a .NET Lambda Layer. (.NET Lambdas just need to manually instrument with the OTel-dotnet SDK).
That's why those "Lambda for .NET" docs say this:
The ADOT Lambda layer provides a reduced version of the AWS Distro for OpenTelemetry Collector, which can further export OpenTelemetry spans to back-end servers.
This layer includes a reduced version of the AWS Distro for OpenTelemetry Collector (ADOT Collector), which runs as a Lambda extension.
I think calling it "Collector layer" was done to avoid any confusion that would come about if it were called ".NET layer" but doesn't actually initialize .NET like I mentioned above.
Hopefully that clears it up 🙂
from aws-otel-lambda.
Closing this issue and please feel free to re-open for any concerns. Thank you 😄
from aws-otel-lambda.
Related Issues (20)
- Support Java 17 runtime for Lambda Layers HOT 2
- Support for Python 3.10 HOT 2
- Allow the source of the parent context to be configurable. HOT 4
- Documentation for S3 Confmap Provider is incorrect HOT 4
- Documentation for included Processors is incorrect HOT 1
- Error exporting traces from Python lambda HOT 2
- Logging exporter does not log metrics or traces HOT 4
- node.js lambda -> aws-otel-lambda -> ADOT collector doesn't work HOT 10
- First set of counter value ignored after lambda cold boot
- Auto-instrumentation Agent only in Lambda HOT 5
- nodejs spans not exported when upgrading aws otel lambda layer to 1.15.0 HOT 7
- How to configure NodeJs auto-instrumentation to use tracecontext instead of xray? HOT 4
- Error invoking Lambda function after adding latest layer (1-28-1) for java HOT 5
- Steps to build and download a private Python lambda layer as a local .zip or .tar file? HOT 1
- Trace is broken in Lambda Java17 Runtime HOT 2
- Traces are not flushed to the server before the lambda terminates HOT 6
- Unable to access Lambda layer for Python with x86_64 architecture HOT 5
- docs: document of supported python version is old HOT 1
- 53612: bind: address already in use HOT 5
- [nodejs lambda layer] no metrics is exported to cloudwatch logs HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from aws-otel-lambda.