-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
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
Azure resultSignature is not necessarily a string #36499
Labels
Comments
eberkut
added
bug
Something isn't working
needs triage
New item requiring triage
labels
Nov 22, 2024
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Triage: Issue appears to be well specified and has necessary info. Moving to |
/label -needs-triage |
/label waiting-for-code-owners |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Component(s)
pkg/translator/azure, pkg/translator/azurelogs
What happened?
Description
The
resultSignature
field in Azure logs is expected to be a string in the codebase:However, this field can vary in type depending on the Azure service emitting the logs. For instance, in Azure AI Search, the
resultSignature
field is an integer as stated in the Azure documentation:https://learn.microsoft.com/en-us/azure/search/monitor-azure-cognitive-search-data-reference#resource-log-schema
This discrepancy causes errors in processing logs from services where
resultSignature
is not a string.Steps to Reproduce
resultSignature
field (e.g., Azure AI Search).resultSignature
field is an integer.Expected Result
Logs from Azure services should be processed without errors, regardless of the type of the
resultSignature
field.Actual Result
An error is generated when processing logs with a
resultSignature
field that is not a string.Collector version
0.114.0
Environment information
Environment
OS: "Ubuntu 20.04"
OpenTelemetry Collector configuration
Log output
Additional context
No response
The text was updated successfully, but these errors were encountered: