opensearch-project / opensearch-project/data-prepper

[BUG] EventName is ignored in the OTel logs source

Open
#6,505 6 comments 1 reaction 1 assignee View on GitHub

@kkondaka is already working on this.

Since Feb 12, 2026.

enhancement
Dominant language
Java
Stars
374
Forks
354
Avg merge
3d 18h
Merged PRs (30d)
8

Description

Describe the bug
The latest OTel log spec has included the EventName in the protocol buffer definition (https://github.com/open-telemetry/opentelemetry-proto/blob/v1.9.0/opentelemetry/proto/logs/v1/logs.proto).

However, the OTel logs source of data prepper does not include this field. When we put the data with the EventName, the EventName will be ignored and will not show in the output.

To Reproduce
Steps to reproduce the behavior:

  1. Create ingestion pipeline with OTel source and any destination
  2. Put the follow testing data to the pipeline endpoint.
awscurl --service osis \
  -X POST \
  "{pipeline_endpoint}/logs" \
  -H 'Content-Type: application/json' \
  -d '{
    "resourceLogs": [{
      "scopeLogs": [{
        "logRecords": [{
          "timeUnixNano": "1739999999000000000",
          "severityText": "ERROR",
          "eventName": "payment.gateway.timeout",
          "body": {
            "stringValue": "Test with EventName field"
          },
          "attributes": [{
            "key": "transaction.id",
            "value": {
              "stringValue": "txn-67890"
            }
          }]
        }]
      }]
    }]
  }'
  1. Verify the data in the destination

Expected behavior
The EventName field should be shown in the destination

Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

  • OS: [e.g. Ubuntu 20.04 LTS]
  • Version [e.g. 22]

Additional context
The issue should stem from the following code.
https://github.com/opensearch-project/data-prepper/blob/main/data-prepper-plugins/otel-proto-common/src/main/java/org/opensearch/dataprepper/plugins/otel/codec/OTelProtoOpensearchCodec.java#L298-L327

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.