Alexander Wert

Hi, yes would be great if you could submit a patch for this.

Need to add handling of distributed tracing / span links for SQS and SNS for AWS Lambda instrumentation

> I don't think it's a good idea to replace concrete terms used on a specific platform with generic cross platform terms. There are subtleties in the terminology, and if...

> and in regards to common metrics with different types of values I think it'd be better to define an additional field/label for the device type (ios vs android) OK,...

> That may also not be that simple for agents though, as it would involve changing the way requests are sent (as multipart content, with one part being metadata and...

> @AlexanderWert did you do the mapping of the [Otel Semantic Attributes for Databases](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/database.md) with the Elastic fields? We have some basic mapping in the [OTel bridge spec PR](https://github.com/elastic/apm/pull/516) but...

With https://github.com/elastic/ecs/pull/1628, there is now a self-nesting of cloud fields in ECS under `cloud.target.*`.

We created a new PR to address this proposal: https://github.com/open-telemetry/oteps/pull/222

@carsonip Right now the only case in which I see some value of `transaction.context.request.id` would be for AWS Lambda transactions. BUT: we already capture the request ID for lambda under...

> Does this include adding the option if we don't already support it? Python doesn't have include_process_args. Yes, if the option is missing, then it should be added as part...