Include the Tail Sampling Processor

[seh]

Motivating Problem

When running the OpenTelemetry Collector alongside a Lambda function, it is difficult to coordinate running separate tail sampling proxies like Honeycomb Refinery, for lack of a suitable container orchestration system being available. It would be beneficial to perform tail sampling within the OpenTelemetry Collector running alongside each Lambda function as well.

Proposed Solution

Make the Tail Sampling Processor available as a processor in the OpenTelemetry Collector Lambda layer's build.

Alternatives Considered

Set up a Kubernetes or ECS cluster to run Honeycomb Refinery, and export traces from each OpenTelemetry Collector to Refinery for tail sampling. However, for a system that relies solely on AWS Lambda functions, establishing that separate environment within which to run Refinery is difficult.

Additional Context

I don't know the change in "weight" in the size of the built executable file results from adding this new processor.

[tylerbenson]

@seh any interest in contributing a PR for this?

[seh]

@seh any interest in contributing a PR for this?

Yes, though it would help to have an example that shows similar precedent, in order to help get started and show how large such a patch is likely to become. Do any other components introduced like this come to mind?

[tylerbenson]

Maybe a combination of #959 and #1046?