Unknown processor type "name" for name

[ericksoen]

Overview

I receive an error cannot load configuration: unknown processors type "insert" for insert when I try to use a OpenTelemetry config that includes a processor section to add attributes (regardless of whether it is referenced in a pipeline)

Sample Configuration

receivers:
  otlp:
    protocols:
      grpc:
      http:

exporters:
  otlp:
    endpoint: "api.honeycomb.io:443"
    headers:
      "x-honeycomb-team": "$HONEYCOMB_WRITE_KEY"
      "x-honeycomb-dataset": "$HONEYCOMB_DATASET"
  logging:
  awsxray:

service:
  pipelines:
    traces:
      receivers: [otlp]
      exporters: [awsxray, otlp]
    metrics:
      receivers: [otlp]
      exporters: [logging]

Relevant Lambda logs

START RequestId: 0ff5f447-5f83-415d-8066-be50193a01e6 Version: $LATEST
2021/07/26 20:03:09 [collector] Launching OpenTelemetry Lambda extension, version:  v0.1.0
2021-07-26T20:03:09.359Z	info	service/collector.go:262	Starting otelcol...	{
    "Version": "v0.1.0",
    "NumCPU": 2
}
2021-07-26T20:03:09.370Z	info	service/collector.go:170	Setting up own telemetry...
2021-07-26T20:03:09.370Z	info	service/collector.go:205	Loading configuration...
Error: cannot load configuration: unknown processors type "insert" for insert
EXTENSION	Name: collector	State: Started	Events: []
END RequestId: 0ff5f447-5f83-415d-8066-be50193a01e6
REPORT RequestId: 0ff5f447-5f83-415d-8066-be50193a01e6	Duration: 10010.84 ms	Billed Duration: 10000 ms	Memory Size: 512 MB	Max Memory Used: 49 MB	
XRAY TraceId: 1-60ff14f2-5e0274d9775e9c3a239e57a5	SegmentId: 56412fd70f3e6881	Sampled: true	

Based on the behavior of the Lambda components that are initialized as factory methods, especially attributesprocessor, I would expect this to correctly add attributes to spans.

I have confirmed that when this section is used for a local OTLP exporter that it behaves as expected.

Relevant versions

OpenTelemetry Lambda layer version: arn:aws:lambda:us-east-1:901920570463:layer:aws-otel-python38-ver-1-3-0:1
OpenTelemetry SDK version: 1.3.0
CollectorVersion: v0.1.0

Expected behavior:

1. I can reference a processor in my trace pipeline