fix: Support OTLP event_name field in logs exporter #1088
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
fix: #1078
Problem
The
event_namefield was added to the OTLP LogRecord proto in open-telemetry/opentelemetry-proto#600, but the logs exporter was not handling this field. Previously, event names were set asevent.nameattributes and were captured in labels. With the new dedicated proto field, this information was being dropped.Solution
Map the OTLP
event_namefield to the Cloud Logging LogEntry label"event.name". This approach:event.nameas an attributelabels."event.name"in Cloud Logging