[otelconsumer] Add log record attributes as flattened keys

[khushijain21]

Proposed commit message

The log record attributes added on otelconsumer should be flattened keys (and not nested map structure) for dynamic indexing on ES exporter to work correctly. This is a fix for it

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Related issues

• Fixes [otelconsumer] Set data_stream.dataset & data_stream.namespace attributes to support dynamic index #42623

[elasticmachine]

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

[AndersonQ]

Looks good, I just left a small suggestion

[khushijain21]

/test

[khushijain21]

make -C libbeat check update
Installing mage v1.13.0.
/Users/khushijain/.magefile cleaned
>> fmt - go-licenser: Checking for missing headers
>> fmt - go-licenser: Adding missing headers
>> fmt - goimports: Formatting Go code
>> fmt - autopep8: Formatting Python code
>> check: Checking source code for common problems
Generated fields.yml for libbeat to /Users/khushijain/Documents/beats/libbeat/fields.yml
>> Building libbeat.yml for linux/amd64
>> Building libbeat.reference.yml for linux/amd64
Updating generated files for libbeat
if [ -d /Users/khushijain/Documents/beats/libbeat/_meta/kibana ]; then \
                cp -pr /Users/khushijain/Documents/beats/libbeat/_meta/kibana/* /Users/khushijain/Documents/beats/libbeat/_meta/kibana.generated ; \
        fi

is successful locally

[mauri870]

Sorry, edited you comment by mistake thinking I was replying.

is successful locally

It succeeds for me as well. Try and change the command on CI to run with the verbose flag (-v). You should be able to see the offending change once the job fails. Job is in pipeline.libbeat.yml.

[mauri870]

@khushijain21 I think your failure is related with the conflict, there was another PR that changed the same file, this is likely the cause of the failure you reported.