William Armiros
William Armiros
This issue is to track the stable release of the `OpenTelemetry.Contrib.Instrumentation.AWSLambda` package as stable. Currently it is in beta: https://github.com/open-telemetry/opentelemetry-dotnet-contrib/releases/tag/Instrumentation.AWSLambda-1.1.0-beta1 cc @srprash @lupengamzn
**Is your feature request related to a problem? Please describe.** I would like to be able to instrument common logging libraries like Log4J and Logback to inject trace IDs that...
**Is your feature request related to a problem?** I am unable to easily instrument [aws-sdk-php](https://github.com/aws/aws-sdk-php) clients for tracing. **Describe the solution you'd like** The expected outcome is an instrumentation library...
*Description of changes:* Adds a unit test to verify that we respect if a customer manually sets their Trace Header for an AWS SDK request, and don't overwrite it with...
It'd be nice to configure the log level output to not include some of the more verbose more verbose messages (like logging an entire trace on every retry) when running...
Right now, header data is stored internally using a regular [Map](https://github.com/awslabs/disco/blob/master/disco-java-agent/disco-java-agent-api/src/main/java/software/amazon/disco/agent/event/AbstractProtocolEvent.java#L49). Right now, if you are consuming a `ProtocolEvent` and would like to get header data, you do something like...
It would be nice if the web package had interceptors for [Netty](https://netty.io/) servers, since Netty doesn't use Servlets. The interceptor should publish request/response events with similar information to their Servlet...