Azure Blob Receiver cannot read non-JSON logs

[stuart23]

Component(s)

receiver/azureblob

What happened?

Description

Receiver fails to unmarshal logs that are not in json format.

Steps to Reproduce

Deploy this collector and subscribe to blobs that are not in json format.

Expected Result

We can still parse these logs, although they will be missing a lot of data.

Actual Result

"failed to unmarshal logs: ReadObjectCB: expect { or n, but found...+125 more"

Collector version

v0.107.0

Environment information

Environment

OS: AKS linux

OpenTelemetry Collector configuration

config:
  extensions:
    health_check: {}

  receivers:
    azureblob:
      connection_string: ${env:STORAGE_CONNECTION_STRING}
      logs:
        container_name: "airflow-logs"
      event_hub:
        endpoint: ${env:EVENTHUB_CONNECTION_STRING}

  processors:
    memory_limiter:
      check_interval: 5s
      limit_percentage: 80
      spike_limit_percentage: 25

  exporters:
    debug:
      verbosity: detailed

  service:
    pipelines:
      metrics: null
      traces: null
      logs:
        receivers:
        - azureblob
        processors:
        - memory_limiter
        exporters:
        - debug

    extensions:
    - health_check

Log output

The unmarshalling error message does not make it to the logs, although it should

Additional context

No response

[github-actions]

Pinging code owners:

• receiver/azureblob: @eedorenko @mx-psi

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[hgaol]

Hi @stuart23 , based on source code, it can only unmarshal logs in plog JSON format, which is expected. What's the format of your raw data?

opentelemetry-collector-contrib/receiver/azureblobreceiver/receiver.go

Line 67 in 601a99d

logs, err := b.logsUnmarshaler.UnmarshalLogs(json)

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• receiver/azureblob: @eedorenko @mx-psi

See Adding Labels via Comments if you do not have permissions to add labels yourself.