opentelemetry-lambda icon indicating copy to clipboard operation
opentelemetry-lambda copied to clipboard

Collector ships with deprecated logging exporter, not the modern debug exporter

Open lpetrazickisupgrade opened this issue 1 year ago • 0 comments

Describe the bug The OpenTelemetry Lambda layer docs say to use the debug exporter: https://opentelemetry.io/docs/faas/lambda-collector/

However, the collector layer ships with the deprecated logging exporter, not the current debug exporter: https://github.com/open-telemetry/opentelemetry-lambda/blob/layer-collector/0.8.0/collector/go.mod#L148

Steps to reproduce Include configuration for the debug exporter:

exporters:
  debug:

What did you expect to see? A working OpenTelemetry Collector layer.

What did you see instead?

{
  "level": "info",
  "ts": 1719433288.313658,
  "msg": "done",
  "error": "unable to start, otelcol state is 3; request failed with status 403 Forbidden",
  "errorCauses": [
    {
      "error": "unable to start, otelcol state is 3"
    },
    {
      "error": "request failed with status 403 Forbidden"
    }
  ]
}
{
  "level": "warn",
  "ts": 1719433288.8894677,
  "logger": "lifecycle.manager",
  "msg": "Failed to start the extension",
  "error": "failed to get config: cannot unmarshal the configuration: 1 error(s) decoding:\n\n* error decoding 'exporters': unknown type: \"debug\" for id: \"debug\" (valid values: [logging otlp otlphttp prometheusremotewrite])"
}

What version of collector/language SDK version did you use? Version: layer-collector/0.8.0 with v0.102.1

What language layer did you use? Config: Python

Additional context I'm attempting to use the layers in a container lambda, so I'm building the git tags locally to add to the container image

lpetrazickisupgrade avatar Jun 26 '24 20:06 lpetrazickisupgrade