Error exporting traces from Python lambda about aws-otel-lambda HOT 2 CLOSED

Update: After reading aws-otel-collector/issues/1757, I realized that:

1. This error was coming from the auto-instrumentation SDK
2. However, within the SDK, it was not coming from the OTLP trace exporter, but rather from the OTLP metrics exporter (link)

Specifically, it looks like the auto-instrumentation SDK was exporting both traces and metrics but, since my collector only had a traces pipeline defined, the SDK metrics exporter was throwing a 404 error.
Once I added a metrics pipeline to my collector (in addition to the existing traces pipeline), the error went away.

So, for this collector config:

receivers: 
  otlp: 
    protocols: 
      grpc: 
        endpoint: 'localhost:4317'
      http: 
        endpoint: 'localhost:4318'

exporters: 
  logging:

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

I get this lambda output:

...
START RequestId: 4b90dbd1-5f7f-4300-b89b-c54e36cf3637 Version: $LATEST
{
    "level": "info",
    "ts": 1687275266.5785906,
    "msg": "TracesExporter",
    "kind": "exporter",
    "data_type": "traces",
    "name": "logging",
    "#spans": 1
}

END RequestId: 4b90dbd1-5f7f-4300-b89b-c54e36cf3637
...

So, at this point, I've gotten rid of the error messages, but I'm still facing an issue: The collector's logging exporter only prints trace info when debug logging is enabled, and never prints metric info (regardless of whether debug logging is enabled or not). For simplicity though, I think I'll go ahead and close this issue, and move the remaining problem to a new issue.

from aws-otel-lambda.

So, at this point, I've gotten rid of the error messages, but I'm still facing an issue: The collector's logging exporter only prints trace info when debug logging is enabled, and never prints metric info (regardless of whether debug logging is enabled or not). For simplicity though, I think I'll go ahead and close this issue, and move the remaining problem to a new issue.

Update: Opened new issue #616 to deal with the remaining, real problem.

from aws-otel-lambda.