We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
receiver/azureblob
Receiver fails to unmarshal logs that are not in json format.
Deploy this collector and subscribe to blobs that are not in json format.
We can still parse these logs, although they will be missing a lot of data.
"failed to unmarshal logs: ReadObjectCB: expect { or n, but found...+125 more"
v0.107.0
OS: AKS linux
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
The unmarshalling error message does not make it to the logs, although it should
No response
The text was updated successfully, but these errors were encountered:
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself.
Sorry, something went wrong.
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
No branches or pull requests
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
Log output
Additional context
No response
The text was updated successfully, but these errors were encountered: