Ensure beats receivers log the same metadata as beats processes #8606

swiatekm · 2025-06-20T14:07:24Z

What does this PR do?

It ensures logs from beats receivers forwarded by elastic-agent have the same metadata as ones from beats processes. It's worth noting they aren't identical, as beats receiver logs currently have the following additional attributes:

otelcol.component.id
otelcol.component.kind
otelcol.signal
resource

Whether these should exist as they are is a separate issue. This PR is only concerned with the backwards compatibility of beats receiver logs relative to beats process logs.

The only semantic change in this PR is passing the base logger to the Otel Collector instead of the elastic-agent logger. This is consistent with what we do for beats processes.

I've also added a test that compares a specifically chosen log line between beats receivers and processes without sending it to Elasticsearch. My intent was to verify the metadata before it goes through any processing pipelines, be they local or remote.

Why is it important?

Beats receivers should be as similar to beats processes as possible in all of their external outputs. Some of the log messages are different during startup, as it uses different code paths, but most of them are identical. More importantly, the metadata used to query these logs in ES must be identical.

Checklist

I have read and understood the pull request guidelines of this project.
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/fragments using the changelog tool~~
I have added an integration test or an E2E test