expose event_name in log context

[tdelabro]

Component(s)

No response

Is your feature request related to a problem? Please describe.

https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/pkg/ottl/contexts/ottllog

Here are listed all the field I can access in stuffs like transform: log_statments but it doesn't expose the event_name field, while this one is part of the context.

I get this error:

Error: invalid configuration: processors::transform: unable to parse OTTL statement "set(log.attributes[\"event_name\"], log.event_name)": error while parsing arguments for call to "set": invalid argument at position 1: segment "event_name" from path "log.event_name" is not a valid path nor a valid OTTL keyword for the log context - review https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/pkg/ottl/contexts/ottllog to see all valid paths

when doing:

  transform:
    error_mode: ignore
    log_statements:
    - context: log
      statements:
      - set(attributes["event_name"], event_name)

Describe the solution you'd like

I would like to be able to access it.

I need it for Loki

Describe alternatives you've considered

No response

Additional context

No response

[github-actions]

Pinging code owners for pkg/ottl: @TylerHelmuth @evan-bradley @edmocosta. See Adding Labels via Comments if you do not have permissions to add labels yourself. For example, comment '/label priority:p2 -needs-triaged' to set the priority and remove the needs-triaged label.

[edmocosta]

I think it's a valid request, here's the proto: https://github.com/open-telemetry/opentelemetry-proto/blob/main/opentelemetry/proto/logs/v1/logs.proto#L224. Changing the event's name might produce invalid events, but I think it should be an user's concern, not OTTL.

[evan-bradley]

@tdelabro I agree this makes sense. Would you be interested in working on this?

[tdelabro]

I could, if it is under 1/2 day of work. I don't have the bandwidth to spend days exploring the codebase, sorry, so I need clear guidance on where is everything that needs to be changed.

[edmocosta]

Hi @tdelabro, I can handle that, no worries. Thank you again for opening this issue.