[pkg/translator/azurelogs] Support additional fields not in the common schema#46165
[pkg/translator/azurelogs] Support additional fields not in the common schema#46165rafaelrodrigues3092 wants to merge 16 commits intoopen-telemetry:mainfrom
Conversation
|
Welcome, contributor! Thank you for your contribution to opentelemetry-collector-contrib. Important reminders:
A maintainer will review your pull request soon. Thank you for helping make OpenTelemetry better! |
|
Should we not be looking to introduce this in the unmarshaller so that we have consistency etc. |
|
/workflow-approve |
MikeGoldsmith
left a comment
There was a problem hiding this comment.
Looks good to me - thanks @rafaelrodrigues3092 👍🏻
|
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
|
Not stale - please can someone from @open-telemetry/collector-contrib-approvers review? |
axw
left a comment
There was a problem hiding this comment.
@rafaelrodrigues3092 sorry for the delay. Looks good overall, just one question.
|
Please address the CI and mark ready for review again. |
|
lint issues fixed. Should be ready for review |
Description
Azure resource logs are not standard, see Common and service-specific schemas for Azure resource logs.
When consuming resource logs for services like Service Bus or Event Hub, timestamp parsing fails.
The log events are also not helpful identifying the resource or resource type causing the parsing issue.
This change:
EventTimeString,EventTimestamp,startTimeEventPropertiesLink to tracking issue
Fixes #46162
Testing
Documentation
Updated Azure Event Hub Receiver ReadMe to include the additional supported fields.
Additional Notes
Assisted-by: Claude Opus 4.6